Return Simply Estate's frequently-asked questions and answers (fees, regulation, IHT, trusts, wills/LPAs/probate). Optional keyword filter.
| Name | Required | Description | Default |
|---|---|---|---|
| query | No | Optional keyword to filter the FAQs |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided; description discloses it returns questions and answers but lacks details on side effects, rate limits, or authentication requirements, which is minimal for a read-only tool.
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?
Single sentence that efficiently conveys purpose, scope, and optional filter, with no extraneous words.
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 tool with one optional parameter and no output schema, the description is adequate but does not specify return format, pagination, or behavior without query.
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% for the single parameter; description adds no new meaning beyond 'Optional keyword filter' which parallels the schema's description.
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?
Description clearly states it returns FAQs with specific topics (fees, regulation, IHT, trusts, wills/LPAs/probate), distinguishing it from sibling tools which are calculations and checks.
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?
Implied use for general FAQ queries but no explicit guidance on when to use versus alternatives or what not to use it for.
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.
Each tool targets a distinct aspect of UK estate planning (IHT, probate, LPAs, trusts, care costs, etc.) with clear boundaries. No overlap in purposes; an agent can easily distinguish between them.
All tool names follow a consistent verb_noun snake_case pattern (e.g., calculate_iht, check_need_probate, lookup_glossary). The naming is predictable and aids in understanding the function of each tool.
16 tools is well-scoped for an estate planning domain. It covers major areas without being overwhelming, and each tool serves a clear purpose without redundancy.
The tool set covers key estate planning topics (IHT, probate, LPAs, trusts, gifts, intestacy, care costs, will readiness). Minor gaps exist (e.g., no tool for creating documents), but the consultation tool directs users to professional advice. Overall, a comprehensive educational surface.
