Retrieve the parent chapter, sibling sections, children, and cross-references of a building-code section to understand its context.
What surrounds a section: parent chain up to the chapter, previous/next siblings, children, and the sections that reference it. Use for 'where does this sit' or 'what else applies' questions.
| Name | Required | Description | Default |
|---|---|---|---|
| corpus | No | ||
| number | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description explains what kind of information is surfaced and implies a read-only lookup, but with no annotations it does not explicitly state side effects, permissions, or that no modifications are made.
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 focused sentence followed by a short use-case clause, with no redundant or extraneous content.
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 context lookup with no output schema, the description enumerates the returned context categories and typical use cases. It could be more complete by defining the parameters, but the core behavior is understandable.
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?
The schema provides no parameter descriptions, and the description does not clarify what 'number' refers to or how 'corpus' is used. The words 'section' and 'corpus' offer only weak inference.
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?
The description clearly states what the tool does: it returns surrounding context for a section, including parent chain, siblings, children, and referencing sections. It also names concrete question types it supports.
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?
It explicitly tells when to use the tool ('where does this sit' or 'what else applies' questions), giving an agent clear selection criteria.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.