RooQuiz

Set dimension analysis

set_dimension_analysis

Destructive

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.

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 already indicate destructiveHint=true and openWorldHint=true, but the description adds substantial context beyond that: it discloses that the dimension list is replaced while overallAnalysis is preserved, that dimensions referenced by question dimensionScores or report.formula cannot be removed, and that code stability is maintained for dimensions with the same name. There is no contradiction; the description enhances the annotation. It clearly warns about irreversible replacement and scene-specific behavior.

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

Conciseness4/5

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

The description is dense and long, but every sentence contributes essential context. It is front-loaded with the core action and then layers scene-specific rules and constraints. While it is a single block of text rather than bullet points, it is structurally logical and not redundant. It could be slightly more concise, but the content justifies the length.

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?

Given the complexity of the tool (scene-specific dimensions, code stability, reference constraints, clearing behavior), the description is comprehensive. It covers prerequisites, limitations (random_knowledge_quiz unsupported), and interaction rules (e.g., formula cannot reference other dimensions). Since an output schema exists, return values are not needed. Nothing essential is missing.

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

Parameters5/5

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

Although the input schema provides 100% coverage with detailed descriptions, the main description adds meaning beyond the schema by explaining how parameters interact: the stable-code logic (pass code to keep/set, omit to keep by name), the scene-specific requirement for fieldCodes vs formula, and the default behavior for standardScore. This is not a restatement but high-level contextual semantics that an agent needs to construct correct calls.

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?

The description states a specific verb and resource: 'Set the multi-dimension analysis (form.report.dimensionAnalysis) of a form, replacing the dimension list without touching overallAnalysis'. It clearly distinguishes from sibling tools like update_form_settings by focusing on the dimensionAnalysis attribute, and even names the prerequisite get_form call. This is unambiguous and purpose-specific.

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?

The description gives explicit when-to-use guidance: it differentiates the knowledge_quiz scene (requires fieldCodes) from the scored_quiz scene (formula optional), and warns that 'Not supported for random_knowledge_quiz forms'. It also states prerequisites ('Call get_form first to read the question and dimension codes') and provides a clear way to clear the analysis ('Pass an empty dimensions array'). This leaves no ambiguity about when to invoke this tool versus alternatives.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?