list_protocol_versionsRetrieve immutable farm protocol definitions with bounded pagination to inspect version history and avoid inventing missing steps.
List immutable farm protocol definitions with bounded pagination. Never invent missing steps.
| Name | Required | Description | Default |
|---|---|---|---|
| skip | No | ||
| take | No | ||
| farm_id | No |
Changes observed during successful MCP inspections.
v0.2.0Input schema / $schemaAdded value: +"http://json-schema.org/draft-07/schema#"Input schema / properties / take / defaultRemoved value: -50Input schema / requiredRemoved value: -[]v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful context that definitions are immutable and pagination is bounded, but it does not explain pagination behavior or access requirements.
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 sentences with the main purpose front-loaded, so it is efficient overall. The final sentence is slightly extraneous but not enough to hurt conciseness.
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?
For a list tool with no output schema and three undocumented parameters, the description leaves out how to scope by farm_id and how pagination should be used. The annotations cover safety, but the remaining functional gaps are significant.
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 0% for all three parameters. "Bounded pagination" hints at skip/take, but farm_id is never explained, and no parameter constraints or semantics are added beyond the schema types.
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 and resource: "List immutable farm protocol definitions," with scope clarified by "bounded pagination." It does not explicitly distinguish itself from create_protocol_version or workflow-template siblings, so it is clear but not fully differentiated.
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?
Gives no explicit when-to-use guidance versus create_protocol_version or the workflow-template tools. "Never invent missing steps" is an agent instruction, not a condition for selecting this tool over alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.