estate-planning

check_deed_of_variation

Check whether a deed of variation is available — guidance-only eligibility against the s.142 IHTA 1984 conditions: the hard two-year window from the date of death (HMRC does not extend it), adult beneficiaries with capacity, and the agreement of everyone whose share would reduce. Returns yes / no / depends with blockers, goal-mapped possibilities, and an honest note that ALWAYS accompanies the result. No tax outcome is promised — whether it helps depends on the whole estate.

Input Schema

TableJSON Schema

Name	Required	Description
`goal`	Yes	What the family wants the variation to achieve
`allAgree`	Yes	Those affected beneficiaries all agree to the change
`allAdults`	Yes	Every beneficiary whose share would reduce is an adult (18+) with capacity
`deathTiming`	Yes	When the person died — the two-year window is the hard statutory gate

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedJun 27, 2026

TDQS

A4.2/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description discloses key behavioral traits without relying on annotations: it is 'guidance-only', returns 'yes/no/depends with blockers', includes an 'honest note that ALWAYS accompanies the result', and states that no tax outcome is promised. This provides the agent with a clear picture of what to expect.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise (three sentences) and front-loaded with the main purpose. Every sentence adds essential information without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has no output schema, the description adequately explains the return format (yes/no/depends with blockers), lists all eligibility conditions, and includes a disclaimer. It covers the necessary context for an agent to use the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema coverage, the baseline is 3. The description adds value beyond the schema by explaining the 'hard two-year window' and HMRC's stance on extensions, clarifying the deathTiming parameter, and mentioning 'goal-mapped possibilities' for the goal parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's main purpose: 'Check whether a deed of variation is available', with a specific verb and resource. It references the legal conditions under s.142 IHTA 1984, distinguishing it from sibling tools like calculate_iht or check_rnrb.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the use case: checking eligibility for a deed of variation. However, it does not explicitly state when not to use this tool or provide alternatives, leaving the agent to infer from context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All estate-planning tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count5/5

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.

Completeness4/5

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.

Resources

Need Help?