Skip to main content
Glama

site

by com.exittaxestimator

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

submit_enquiry

Submits an enquiry to Exit Tax Estimator — 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 state tax advisers, 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 state tax advisers, 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?

No annotations are provided, so the description carries the full burden. It discloses the two-call behavior, that validation returns a summary/consent line/token, that submission triggers an email the person must click before providers see it, and the exact consent wording. This is strong behavioral disclosure beyond the raw action.

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 dense but every sentence earns its place. The non-purchase disclaimer is front-loaded, Step 1 and Step 2 are cleanly separated, and the consent text is included because it is operationally necessary. No filler or repetition.

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?

The two-step workflow is fully specified: first call with answers and consent to get a summary/token, second call with token only after agreement, and the email-verification requirement. Return values are summarized despite no output schema. The description provides everything an agent needs to invoke 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?

Schema coverage is 100%, so the baseline is 3. The description adds real semantic value by explaining that answers must be keyed by field keys from enquiry_fields and, crucially, that confirmation is the token returned in Step 1 and must be included in Step 2. This goes beyond the schema descriptions.

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 opens with a precise verb and resource: 'Submits an enquiry to Exit Tax Estimator.' It immediately clarifies what the tool is not ('NOT a purchase, NOT a guaranteed quote') and states the two-step nature, making it clearly distinct from sibling tools like enquiry_describe and checker_start.

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 a clear usage flow: Step 1 validates and returns a confirmation token, Step 2 submits only after the person agrees. It also references enquiry_fields for answer keys, implying prerequisite context. It does not explicitly name alternative tools or state when not to use it beyond 'not a purchase,' so it stops short of a 5.

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/5.0
Disambiguation5/5

The tool set cleanly separates into two prefixes: checker_* for the decision guide and enquiry_* for the estimator form. Within each group, each tool has a distinct role: start, answer, tree for the checker; describe, fields, submit for the enquiry.

Naming Consistency5/5

All tool names use snake_case with a consistent domain-prefix pattern: checker_start, checker_answer, checker_tree and enquiry_describe, enquiry_fields, submit_enquiry. The naming makes the grouping and purpose immediately predictable.

Tool Count5/5

Six tools is a well-scoped count for a server covering two distinct workflows: a decision guide and an enquiry submission flow. Every tool earns its place and there is no unnecessary redundancy.

Completeness5/5

The checker workflow is complete: start gives an entry point, answer navigates the tree, and tree allows full end-to-end reasoning. The enquiry workflow is also complete: describe explains the process, fields provides the schema, and submit_enquiry handles the two-step consent and confirmation flow.

Resources