Explore the ancestral lineage and kinship hierarchy of Igbo communities, towns (Obodo), villages (Ogbe), kindreds (Ụmụnna), and family compounds (Obi).
| Name | Required | Description | Default |
|---|---|---|---|
| level | No | Optional hierarchy level filter ('town', 'village', 'kindred', 'family_house') | |
| query | Yes | Town, clan, or kindred name (e.g., 'Ogidi', 'Awka', 'Nnewi', 'Umunna', 'Ikenga') |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description frames the tool as "Explore" and the name is search_lineage, both implying a read-only search. The annotations instead declare destructiveHint=true and readOnlyHint=false, which contradicts the description's framing. No warning about destructive behavior is provided.
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 front-loaded sentence with no redundant wording. It is appropriately sized for a two-parameter search tool.
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 only two parameters and full schema coverage, the basic call is technically possible. However, the description omits any disclosure of the destructive behavior declared by annotations, leaving an agent unable to understand the tool's consequences safely.
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 query and level are fully documented in the schema. The description's enumeration of towns, villages, kindreds, and family compounds loosely aligns with the level filter but adds no syntax or mapping beyond the schema.
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 ("Explore") and resource ("ancestral lineage and kinship hierarchy") and enumerates the relevant Igbo levels: towns, villages, kindreds, and family compounds. It does not explicitly distinguish itself from sibling search tools, but the purpose is clear.
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 gives no when-to-use or when-not-to-use guidance and does not mention alternatives such as search_cultural_archive or lookup_name. Usage is only implied by the topic.
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.