checker_answerGiven a question id and the chosen option (its choice index), return the next question or the final verdict.
| Name | Required | Description | Default |
|---|---|---|---|
| choice | Yes | ||
| question | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
There are no annotations, so the description carries the full burden. It discloses the main behavior (returns next question or verdict) but does not mention edge cases, potential errors (e.g., invalid question ID, out-of-range choice), or whether the state is persisted. These omissions leave some behavioral uncertainty for an agent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is one concise sentence, efficiently packed with the tool's purpose and key parameters. It is front-loaded with the core action and includes the parameter explanation inline, with no redundant content.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no annotations, no output schema, and only two simple parameters, the description is adequate but lacks details about return value structure, error handling, and how this fits with sibling tools. An agent could still use it correctly, but additional context on the question flow (e.g., whether it advances a session) would improve completeness.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has 0% coverage, meaning the description is the only source of parameter meaning. The description explains that `question` is a question id and `choice` is a selected option index, so it adds necessary context. However, it lacks details like how to obtain valid question IDs or the exact format of the `choice` index (e.g., 0-based vs 1-based), though the schema's minimum of 0 suggests 0-based.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states what the tool does: given a question ID and a selected choice (its `choice` index), it returns the next question or the final verdict. This distinguishes it from siblings like checker_start and checker_tree, implying a step-by-step progression rather than starting or viewing the whole tree.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies when to use this tool: when the user has answered a question and needs the next step. It does not explicitly state when not to use it or mention alternatives like checker_start or checker_tree, but the title and context make the use case fairly clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
The tool set cleanly separates two distinct workflows: the checker tools for navigating a decision guide and the enquiry tools for submitting a form. Within each group, every tool has a clearly different role—start, answer, tree, describe, fields, submit—so an agent is unlikely to confuse them.
Most tools follow a resource-prefix pattern such as checker_start, checker_answer, checker_tree, enquiry_describe, and enquiry_fields. The exception is submit_enquiry, which uses verb_noun form instead of the enquiry_ prefix, and checker_start/answer/tree mix verb and noun suffixes, creating a minor inconsistency.
Six tools is well-scoped for a site with two distinct user-facing features. Each tool serves a necessary step in its workflow, and there are no redundant utilities or excessive entries.
The checker workflow is fully covered: start, per-step answers, and full tree access for validation. The enquiry workflow is also complete with explanation, field schema, and a two-step submission flow that includes consent and confirmation handling.