Skip to main content
Glama

compare_trusts

Recommend which UK trust types are worth discussing for a goal, with an HONEST note that always accompanies the recommendation (e.g. no trust simply avoids care fees — deliberate-deprivation rules apply with no time limit). Each trust lists what it does NOT do. 'No trust may be needed' is a valid answer.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
goalYesWhat the person is trying to achieve

Schema Changelog

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

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations, the description carries full behavioral burden. It discloses an honest note that always accompanies recommendations, example of care fees limitation, and that no trust may be needed. This provides significant transparency beyond basic purpose.

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 three sentences, each adding essential information: purpose with honest note, output characteristics, and a valid null result. No wasted words, effectively front-loaded.

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 one required parameter and no output schema, the description adequately covers what the tool does and what to expect. It could briefly mention return format, but is sufficient for agent use.

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

Parameters3/5

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

Schema coverage is 100% with one parameter 'goal' having enum and description. The tool description does not add extra detail on the parameter itself but contextualizes its usage. Baseline 3 is appropriate as schema already documents the 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 recommends UK trust types for a goal, with an honest note and lists what each trust does not do. This distinguishes it from sibling tools like calculate_iht or check_rnrb which focus on other estate planning aspects.

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

Usage Guidelines4/5

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

The description implies use when a user has a goal and needs trust recommendations. It does not explicitly state when not to use or mention alternatives, but the context is clear enough for an agent to differentiate from sibling tools.

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

Try in Browser

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