list_form_responsesRead the responses submitted to a form — each submission's answers and when it arrived, newest first. Requires event_id + form_id; you must be a host. Read-only.
| Name | Required | Description | Default |
|---|---|---|---|
| form_id | Yes | ||
| event_id | Yes |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Description adds that responses are returned newest first and requires host authorization, complementing annotations (readOnlyHint, destructiveHint). No contradictions.
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 concise sentences with critical info front-loaded. No unnecessary words.
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?
Describes what is returned (answers and timestamp, newest first) and access requirement. Lacks pagination details but acceptable for a simple read tool.
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 has 0% parameter description coverage; description only lists event_id and form_id as required but adds no further meaning about what they represent or their constraints.
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?
Clearly states the tool reads form responses, specifies resource and verb. Differentiates from siblings like 'export' and 'list_forms' by focusing on reading submitted responses.
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?
Explicitly requires event_id and form_id and mandates host role. Read-only is stated. Could mention alternatives but not necessary for basic usage.
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.