Skip to main content
Glama

site

by com.exitvaluecalculator

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

submit_enquiry

Submits an enquiry to Exit Value 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 relevant tax adviser, 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 relevant tax adviser, 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.9/5.0
Behavior5/5

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

No annotations are provided, so the description carries the full burden. It discloses the two-step submission flow, that step 1 returns a summary and token, that an email with a link is sent in step 2, and that providers only see the enquiry after the link is clicked. It even states the exact consent sentence.

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?

Long but tightly organized around two numbered steps with no filler. Key constraints ('NOT a purchase, NOT a guaranteed quote') are front-loaded, and every sentence conveys a requirement or consequence the agent needs.

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?

For a complex two-step tool with no output schema and no annotations, this is unusually complete: it defines inputs, step boundaries, validation behavior, approval condition, consent text, confirmation token, email link, and provider visibility. No critical invocation detail is missing.

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 baseline is 3. The description adds meaningful semantics beyond the schema: answers keyed by enquiry_fields, consent means the person has read and agreed to the exact quoted line, and confirmation is the token from step 1 after approval.

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?

States a specific action ('Submits an enquiry' to Exit Value Calculator), explicitly distinguishes it from a purchase or guaranteed quote, and gives a two-step flow that differentiates it from sibling tools like calculate or enquiry_describe. The two-step narrative resolves any ambiguity in the name.

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

Usage Guidelines5/5

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

Gives explicit when-to-call instructions: first call with answers and consent for validation and summary, second call with same answers, consent, and confirmation token only after the person agrees. It also provides the exact consent wording and the condition for proceeding.

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

A4.1/5.0
Disambiguation5/5

Each tool has a distinct purpose: calculate runs the tax calculator, calculator_describe explains its inputs/outputs, enquiry_describe explains the enquiry process, enquiry_fields lists form fields, and submit_enquiry performs the submission. There is no overlap between any of them, making selection unambiguous.

Naming Consistency3/5

Naming mixes patterns: 'calculate' is a bare verb, 'calculator_describe' and 'enquiry_describe' use noun_verb, 'enquiry_fields' uses noun_noun, and 'submit_enquiry' uses verb_noun. While the pattern is not uniform, each name still conveys its function reasonably well, and the mixing is not chaotic.

Tool Count5/5

Five tools is a well-scoped set for a server that handles both a calculator and an enquiry form. Each tool addresses a necessary step (describe, calculate, fields, submit), with no redundancy or excessive bloat.

Completeness5/5

The server covers the full workflow: for the calculator, it provides execution and documentation; for the enquiry, it provides process description, field listing, and submission with a two-step confirmation. There are no obvious missing operations for the stated domain.

Resources