Skip to main content
Glama

RooQuiz

by com.rooquiz.payload

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
NameRequiredDescriptionDefault
titleNoMulti-dimension analysis title
formIdYesThe form ID to configure
dimensionsNoThe dimension list (at most 50). Pass an empty array to clear the multi-dimension analysis.
showRadarChartNoWhether to show the radar chart, default true
showStandardLineNoWhether to show the standard-score line on the radar chart

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
formIdNoThe form that was edited
dimensionsNoThe dimensions after the replace
dimensionCountNoHow many dimensions are configured now (0 = cleared)

Schema Changelog

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

  1. Changed4 schema fields changed
    • 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."
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false and destructiveHint=false, so the description carries the behavioral burden and it excels: it discloses partial-update behavior (omitted title/radar settings are kept), dimension code stability rules, the removal constraint for dimensions referenced by question dimensionScores or report.formula, scene-dependent treatment of formula/fieldCodes, and the standardScore auto-computation defaults. Notably it tempers destructiveHint=false by explaining exactly what can and cannot be removed, with no contradiction to the annotations.

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?

A single dense paragraph of roughly 230 words that is front-loaded with the core purpose and where every sentence carries operational information. It loses one point because the dense wall-of-text formatting makes scene-specific rules harder to scan — short scene-labeled segments or bullets would improve parseability — but there is no padding or redundancy.

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, nested dimension objects, two scene variants, and an output schema, the description covers everything an agent needs to call it correctly: prerequisites, unsupported forms, preservation semantics, code stability, removal constraints, and clearing behavior. Return values are already handled by the output schema, so their absence from the description is not a gap. The only minor omission is explicit error behavior for invalid references, which the schema partially covers ('Each code must exist in the form').

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%, so the baseline is 3, and the description adds meaningful cross-parameter semantics beyond individual schema descriptions: which parameters apply in which scene, how formula and fieldCodes interact, how standardScore defaults are derived, and how the empty dimensions array triggers a clear. It does not need to restate per-field constraints since the schema already documents them, but the scene-conditional behavior is genuine added value, warranting a 4.

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?

Opens with a specific verb-resource pair — 'Set the multi-dimension analysis (form.report.dimensionAnalysis) of a form' — and immediately clarifies the exact mutation semantics: replaces the dimension list while preserving overallAnalysis. It is clearly distinguishable from all siblings (update_form, create_form, get_form) because it names the precise report field it operates on and states its unsupported form type.

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?

Gives explicit when-to-use conditions per scene ('In the knowledge_quiz scene each dimension needs fieldCodes; in the scored_quiz scene a formula is optional'), an explicit when-not ('Not supported for random_knowledge_quiz forms'), a prerequisite ('Call get_form first to read the question and dimension codes'), and a clear usage pattern for clearing ('Pass an empty dimensions array'). This is actionable routing guidance, not just a generic statement of purpose.

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

All RooQuiz toolsInspect
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.1/5.0
Disambiguation4/5

Most tools map to a distinct resource and action, and the descriptions actively disambiguate similar operations (e.g., get_form vs get_form_share_info vs get_form_stats). The main potential confusion is between list_records and list_leads and between get_record and get_lead, since both describe leads from slightly different angles.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun convention, with resources like form, question, lead, booking, examinee, translation, and tenant parallel across actions. The few non-CRUD verbs like prepare_/finalize_, duplicate_, and reschedule_ still fit the same uniform pattern.

Tool Count2/5

48 tools is well beyond the 3–15 ideal and even past the 25+ threshold, making the tool surface heavy for an agent to navigate. The broad platform scope explains some of the size, but the count still risks overwhelming context and increasing misselection.

Completeness4/5

The server covers form lifecycle, question editing, translations, CRM leads, examinees, records, bookings, team/tenant operations, image uploads, templates, and analytics extremely well. Minor gaps remain—such as no lead/record deletion, no member removal or role updates, and limited booking-settings management—but most workflows can be completed with the existing tools.

Resources