get_rationRetrieve a feed ration by UUID to view its ingredients in load order and assigned groups. Use it to inspect one ration's composition and group links.
Get a single feed ration by its UUID, including its ingredients (in load order) and group assignments.
| Name | Required | Description | Default |
|---|---|---|---|
| farm_id | No | The ID of the farm (optional if a default is set). | |
| ration_id | Yes | The ration UUID. |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The readOnlyHint annotation already makes the safe-read nature clear. The description adds useful return context by noting ingredients in load order and group assignments, but does not mention error behavior, permissions, or whether missing rations return an error.
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 a single, front-loaded sentence with no wasted words. It places the key lookup key and returned data in an efficient order.
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 simple read-only lookup with a fully documented schema and annotations, this is largely complete. It describes the main returned content, though without an output schema the agent still lacks a full picture of all possible response fields.
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%, so both parameters are already documented in the schema. The description reinforces that lookup is by UUID but adds no syntax or constraint details beyond the schema for ration_id or farm_id.
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: get a single feed ration by UUID. The word "single" plus the described ingredients and group assignments distinguish it from list_rations, though no sibling is named explicitly.
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 usage by saying lookup is by UUID, which suggests fetching one known ration rather than listing rations. It does not explicitly say when to use this versus list_rations or other ration-related tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.