RooQuiz

set_dimension_analysis

Set the multi-dimension analysis (form.report.dimensionAnalysis) of a form, replacing the dimension list without touching overallAnalysis (title / radar settings you omit are kept). Dimension codes are stable: pass dimensions[].code to keep or set one, or omit it and a dimension with the same name keeps its existing code. In the knowledge_quiz scene each dimension needs fieldCodes (question codes); in the scored_quiz scene a formula is optional — dimensions that questions score into via choices[i].dimensionScores sum those automatically, so only give a formula to dimensions no question scores directly. A dimension still referenced by a question's dimensionScores or by report.formula (the overall formula) cannot be removed. Pass an empty dimensions array to clear the multi-dimension analysis. Call get_form first to read the question and dimension codes. Not supported for random_knowledge_quiz forms.

Input Schema

TableJSON Schema

Name	Required	Description
`title`	No	Multi-dimension analysis title
`formId`	Yes	The form ID to configure
`dimensions`	No	The dimension list (at most 50). Pass an empty array to clear the multi-dimension analysis.
`showRadarChart`	No	Whether to show the radar chart, default true
`showStandardLine`	No	Whether to show the standard-score line on the radar chart

Output Schema

TableJSON Schema

Name	Required	Description
`formId`	No	The form that was edited
`dimensions`	No	The dimensions after the replace
`dimensionCount`	No	How many dimensions are configured now (0 = cleared)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed4 schema fields changedSep 5, 2026

addedInput schema / properties / dimensions / items / properties / code

Added value: +{
+  "description": "Optional stable identifier for the dimension (same rules as question codes: starts with a letter or underscore, letters/digits/underscores only). Set it when questions reference the dimension via choices[i].dimensionScores in the same create_form call. When updating, pass the existing code to keep it; if omitted, a dimension with the same name keeps its current code, otherwise one is generated.",
+  "maxLength": 64,
+  "type": "string"
+}

changedInput schema / properties / dimensions / items / properties / fieldCodes / description

Previous value: -"Required in the knowledge_quiz scene: the question codes this dimension covers (dimension score = sum of these field scores). Each code must exist in the form. Ignored in the scored_quiz scene."New value: +"Required in the knowledge_quiz scene: the question codes this dimension covers (dimension score = sum of these field scores). Each code must exist in the form. Ignored in the scored_quiz scene, where the formula decides which questions count."

changedInput schema / properties / dimensions / items / properties / formula / description

Previous value: -"Required in the scored_quiz scene: the dimension score formula. Question codes must be wrapped in `{{code}}` (e.g. `{{q1}} + {{q2}}` when you set custom question codes, or `{{__field_abc}} + {{__field_def}}` for auto-generated ones); bare codes are rejected. Supported operators: + - * / ( ). Ignored in the knowledge_quiz scene."New value: +"Required in the scored_quiz scene: the dimension score formula, usually the sum of the questions in this dimension. Question codes must be wrapped in `{{code}}` (e.g. `{{q1}} + {{q2}}` when you set custom question codes, or `{{__field_abc}} + {{__field_def}}` for auto-generated ones); bare codes are rejected. Inside a dimension formula `{{q}}` is the question's score for THIS dimension: its choices[i].dimensionScores override when set, otherwise the plain choice score. A dimension formula cannot reference other dimensions (only report.formula can). Supported operators: + - * / ( ). Ignored in the knowledge_quiz scene."

changedInput schema / properties / dimensions / items / properties / standardScore / description

Previous value: -"Standard score (the radar-chart standard line; in the scored_quiz scene it also acts as the dimension full mark). Default 0."New value: +"Standard score (the radar-chart standard line; in the scored_quiz scene it also acts as the dimension full mark). When omitted in the scored_quiz scene it defaults to the attainable maximum: the formula evaluated with every referenced question at its highest score for this dimension (choices[i].dimensionScores override, else the choice score); 0 when that cannot be estimated, e.g. the formula uses NumberField / date questions. knowledge_quiz defaults to 0."

First observedAug 24, 2026

TDQS

A4.9/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations carry no safety hints (all flags false), so the description bears the full behavioral burden — and it delivers: replacement semantics, preservation of omitted settings, code-stability rule, removal constraints for dimensions referenced by question dimensionScores or report.formula, empty-array clearing behavior, and the unsupported form type. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Seven sentences, each carrying distinct information — core semantics, stability rule, scene requirements, failure mode, clearing behavior, prerequisite, exclusion — with zero redundancy. The core behavior is front-loaded in the first sentence, and the density is justified by the tool's genuine complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 5 parameters, a nested dimensions array, scene-dependent behavior, and an output schema, the description covers mutation semantics, partial-update behavior, failure modes, clearing, prerequisites, and exclusions. An output schema already exists so return values need no explanation. Nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with rich per-field descriptions, so the baseline is 3. The description adds meaningful contextual semantics beyond the schema: the code-stability rule (same name preserves existing code), the automatic summation of choices[i].dimensionScores and when a formula is actually needed, and the removal constraint linking to report.formula. These are behavioral clarifications that the schema's per-field docs do not fully convey.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource — 'Set the multi-dimension analysis (form.report.dimensionAnalysis) of a form' — and precisely describes the mutation semantics: replacing the dimension list while preserving omitted overallAnalysis settings. This clearly differentiates it from general form setters like update_form and update_form_settings among the siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit when-to-use scene guidance (knowledge_quiz requires fieldCodes; scored_quiz makes formula optional with automatic dimensionScores summing), a concrete prerequisite ('Call get_form first to read the question and dimension codes'), and a clear when-not exclusion ('Not supported for random_knowledge_quiz forms'). An agent knows exactly when and how to invoke this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All RooQuiz tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0

Disambiguation4/5

Most tools have clearly distinct purposes, especially the form, question, and translation families. The main ambiguity is between the lead/record tools: list_leads/get_lead vs list_records/get_record both describe entities as 'leads' even though one is the CRM lead and the other is the submission record. update_form vs update_form_settings is also a minor naming overlap, but the descriptions resolve it.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern: get_*, list_*, create_*, update_*, delete_*, add_*, set_*, etc. Even paired image upload tools follow the same convention with prepare_/finalize_. There is no camelCase or mixed verb-style chaos.

Tool Count2/5

48 tools is far above the 25-tool threshold for a heavy tool surface. While the server covers a broad platform (forms, translations, leads, bookings, examinees, tenants, images), the sheer number will burden an agent's tool-selection step. Each tool may earn its place, but the overall set is too large for easy navigation.

Completeness4/5

The toolset provides solid lifecycle coverage for forms, questions, translations, leads, bookings, examinees, and tenant administration. Minor gaps exist, such as no lead deletion/export and no way to create or delete examinees, but agents can work around these for the core quiz-and-CRM workflow. The form/translation/question CRUD surface is especially thorough.

Resources

Need Help?