Submit up to 50 profile question answers in one batch to complete questionnaires, supporting multiple-choice, yes/no, free-form, fill-in-blank, and varied answer sources.
Submit multiple answers at once (up to 50). Useful for completing questionnaires.
| Name | Required | Description | Default |
|---|---|---|---|
| answers | Yes | Array of answers to submit (1-50 items) |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so the description carries the full behavioral burden. It discloses the 50-item cap but nothing about atomicity (does one bad answer fail the whole batch?), validation behavior, partial success, or required permissions for a mutation operation.
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?
Two short, front-loaded sentences with no waste. The limit is stated immediately after the verb, which is the right emphasis.
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?
A batch mutation tool with no annotations, no output schema, and no disclosure of atomicity, validation, or failure semantics. An agent cannot predict what happens when one answer in the array is invalid, which is critical for a write operation.
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?
Schema coverage is 100% and the schema fully documents the nested answer structure, including per-type fields. The description only restates the batch limit, adding nothing beyond the schema. Baseline 3 is appropriate.
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?
States a specific verb (submit) and resource (answers), plus the batch scope ('multiple at once, up to 50'). Distinguishes itself from the singular sibling submit_answer via 'multiple', though it doesn't name it or explicitly contrast.
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?
'Useful for completing questionnaires' implies a context but gives no when-to-use vs when-to-prefer the singular submit_answer, no exclusions, and no guidance on error handling for batches.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.