Skip to main content
Glama

site

by uk.settlementcalculator

Submit an ENQUIRY to human providers (two steps; not a purchase)

submit_enquiry

Submits an enquiry to Settlement Calculator — NOT a purchase, NOT a guaranteed quote. Step 1: call with the answers (keyed by field key from enquiry_fields) and consent=true; it validates and returns a summary, the consent line and a confirmation token — show the person the summary and the consent line. Step 2: only if the person agrees, call again with the same answers, consent=true and the confirmation token; the enquiry is then submitted, and the person receives an email with a link they must click before any provider sees it. Consent means the person has read and agreed to: "Happy for my details to go to a specialist employment solicitor, who'll contact me directly."

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
answersYesthe person's answers, keyed by field key
consentYestrue only when the person has agreed to: Happy for my details to go to a specialist employment solicitor, who'll contact me directly.
confirmationNothe confirmation token from step 1, after the person has approved the summary

Schema Changelog

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

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the full burden of behavioral disclosure and does so thoroughly. It explains validation in step 1, that the enquiry is only submitted in step 2, that the person must click an email link before providers see it, and the exact consent wording the person must have agreed to.

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 long but every sentence earns its place: it front-loads the key warning, then clearly separates the two steps with conditions and outcomes. The structure makes the multi-step flow easy to follow without unnecessary detail.

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

Completeness5/5

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

Despite having no output schema or annotations, the description covers validation behavior, the summary/consent line/token returned in step 1, the condition for step 2, and the email-link requirement. An agent has enough context to invoke this tool correctly through both steps.

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?

Schema coverage is 100%, so the baseline is 3. The description adds meaningful context by linking answers to enquiry_fields, explaining that consent requires agreement to a specific statement, and clarifying that confirmation is the token returned in step 1 and reused in step 2.

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 it submits an enquiry to Settlement Calculator and immediately differentiates it from a purchase or guaranteed quote. It also conveys the two-step nature up front, which distinguishes it from simpler sibling tools like calculate or enquiry_fields.

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 gives an explicit step-by-step protocol: call once to validate, show the summary, then call again only if the person agrees. It clearly states when step 2 is appropriate and warns that this is not a purchase/quote, but it does not name sibling alternatives explicitly.

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

All site toolsInspect
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

A3.9/5.0
Disambiguation4/5

Each tool has a clear role: calculate runs the estimator, the describe/fields tools provide reference information, and submit_enquiry handles the enquiry flow. There is minor potential confusion between calculator_describe and enquiry_describe since both are describe-style tools, but their targets are clearly different.

Naming Consistency2/5

Tool names mix patterns: 'calculate' and 'submit_enquiry' are verb-first, while 'calculator_describe' and 'enquiry_describe' are noun-first, and 'enquiry_fields' is noun-only. The inconsistent ordering makes the set feel less predictable than it could be.

Tool Count5/5

Five tools is a well-scoped size for a site centered on a settlement calculator and an enquiry submission flow. Each tool covers a distinct need without bloat or unnecessary granularity.

Completeness5/5

The surface covers the full expected lifecycle: running the calculator, understanding its inputs/outputs, understanding what the enquiry does, retrieving the enquiry fields, and submitting the enquiry with confirmation handling. No obvious dead ends or missing operations for the stated domain.

Resources