Get one of your capsules by capsule_id
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"capsule_id": "<capsule_id>"
},
"name": "hib_get_capsule"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| capsule_id | Yes |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden and says nothing beyond retrieval. It does not confirm this is a read-only operation, what happens with an unknown id, or whether the capsule's content is returned in full.
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 short, front-loaded sentence with no filler. Its brevity is also its weakness — the minimal size reflects under-specification rather than tight editing.
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?
With no output schema and no annotations, the description should explain what a returned capsule contains and the id's origin. Neither is present, leaving a bare one-parameter tool still under-described.
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 0% and capsule_id is an untyped-in-practice string with no format described. The description only repeats the parameter name; it never says where the id comes from (e.g., hib_list_capsules results).
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 plus the lookup key: 'Get one of your capsules by capsule_id'. The word 'one' distinguishes it from hib_list_capsules implicitly, 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?
No statement of when to use this instead of hib_list_capsules or how a capsule_id is obtained. The only hint is the required id in the schema, leaving the routing decision to inference.
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.