Retrieve a single form by UUID, including its fields, settings, and submission count, to inspect form configuration and usage.
Get a single form with fields, settings, and submission count.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Form UUID |
Changes observed during successful MCP inspections.
v4.71.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden. It discloses the read shape (fields, settings, submission count), which tells the agent this is a non-destructive lookup, but says nothing about permissions, error behavior for a bad UUID, or whether submission count is computed live.
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?
A single front-loaded sentence with no filler; the only shortcoming is that brevity here is close to under-specification.
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?
There is no output schema, so the description must carry return semantics — it names three returned components but not their structure, pagination of submission counts, or failure modes. Adequate but thin for a fetch-by-id tool with no annotations.
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 description coverage is 100% and the single 'id' parameter is documented as a Form UUID, so the baseline of 3 applies. The description adds nothing about the identifier beyond what the schema already states.
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?
Specific verb+resource ('Get a single form') plus the payload contents, which distinguishes it from the sibling list tools conduyt_list_forms and conduyt_list_form_submissions. Sibling differentiation is implicit rather than stated.
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?
'Get a single form' implies the caller already has an identifier, which is the natural differentiator from list_forms, but the description never names an alternative or states when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.