RooQuiz

get_form

Read-only

View one form of the current team in full, including the questions list fields[] and the report configuration. For outcome forms, the outcome codes that question votes reference live in report.outcomeAnalysis.outcomes. language is the primary language; existing non-primary language versions are listed in translationLanguages.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	The form UUID
`includeFields`	No	Whether to return fields[] (raw data of questions + page breaks), default true. For large forms you can pass false to skip
`includeReport`	No	Whether to return the report configuration, default true

Output Schema

TableJSON Schema

Name	Required	Description
`id`	No	Form id
`scene`	No	knowledge_quiz / scored_quiz / outcome_quiz
`theme`	No	Answer-page theme name
`title`	No	Form title
`fields`	No	Full question list with code / choices / scoring (only when includeFields)
`report`	No	Report configuration, trimmed to the scene (only when includeReport)
`isActive`	No	Whether the form is open for submissions
`language`	No	Primary language
`shareUrl`	No	Public share / answer link
`createdAt`	No	ISO datetime
`openGraph`	No	Social share card { title, description, image, keywords }
`updatedAt`	No	ISO datetime
`systemText`	No	Overridden system copy, keyed by text key
`description`	No	Form description
`publicToken`	No	Token behind the public answer link
`translationLanguages`	No	Languages that already have a translation

TDQS

A4/5.0

Behavior4/5

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

Annotations already mark this as read-only and non-destructive; the description adds value by revealing where outcome codes live and how language versions are represented. This is helpful context beyond the annotations, though it does not discuss errors or edge cases.

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?

The description is compact, front-loaded, and every sentence carries meaningful scoping or nesting information. It is easy to scan and contains no filler.

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

Completeness4/5

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

Given the read-only annotations, full schema coverage, and presence of an output schema, the description covers what an agent needs to invoke the tool successfully. It also provides helpful pointers into the response structure, though it could clarify the active-tenant context slightly more explicitly.

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

Parameters3/5

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

The input schema has 100% coverage and clearly documents id, includeFields, and includeReport with defaults. The description mentions fields[] and report configuration but does not add much parameter-specific guidance beyond what the schema already provides.

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 uses a specific verb ('View one form of the current team in full') and explicitly names the main contents: questions fields[] and the report configuration. This clearly distinguishes it from sibling tools like list_forms, get_form_translation, and get_form_funnel.

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

Usage Guidelines3/5

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

The description implies when to use it — when a single form's full configuration is needed — but it does not explicitly contrast the tool with alternatives or provide when-not-to-use guidance. The 'current team' scope is useful, but the choice between this and related getters is left to the agent.

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.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

Need Help?