clause_getRetrieve a full contract clause by ID or partial title, including its variables and revision count in Pro, to locate and reuse standard terms.
Return a clause in full by id or by title, with its variables and, in Pro, its revision count.
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | Clause id, for example late-fees | |
| title | No | Clause title; a partial title matches too |
Changes observed during successful MCP inspections.
v0.20.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries the full burden. It mentions the 'Pro' revision-count behavior but omits error handling, precedence rules, or any side effects.
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 sentence that is compact and directly states the action, target, and notable output detail.
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 the return value but leaves gaps around parameter requirements, not-found behavior, and interaction between id and title. Adequate for a simple read but not fully complete.
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 covers both parameters with short descriptions; the tool description repeats them but adds little beyond the schema, so it meets the baseline for high coverage.
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 ('Return') and resource ('a clause in full'), with details about variables and revision count that distinguish it from list/search operations.
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?
Clearly indicates retrieval by id or title, but does not explicitly mention when to prefer list/search alternatives or what happens if both parameters are omitted.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.