Skip to main content
Glama

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

submit_enquiry

Submits an enquiry to Taxooor: 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 the Taxooor team sees it. Consent means the person has read and agreed to: "By submitting you agree Taxooor may reply to your question by email. We do not sell your details to anyone."

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "answers": "<answers>",
      "consent": "<consent>"
    },
    "name": "submit_enquiry"
  }
}

Input Schema

NameRequiredDescriptionDefault
answersYesthe person's answers, keyed by field key
consentYestrue only when the person has agreed to: By submitting you agree Taxooor may reply to your question by email. We do not sell your details to anyone.
confirmationNothe confirmation token from step 1, after the person has approved the summary

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

No annotations exist, so the description carries the full burden and does so: it discloses validation behavior, the exact return payload of step 1 (summary, consent line, token), the double opt-in gate (the person must click an emailed link before the Taxooor team sees the enquiry), and the verbatim consent text. The key non-obvious traits — that this is not a purchase, not a guaranteed quote, and not visible to the team until confirmed — are all surfaced.

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

Conciseness4/5

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

Front-loaded with the disclaimers, then cleanly structured as Step 1 / Step 2 with no filler. The consent sentence is quoted verbatim in both the description and the consent parameter schema, which is slight duplication, though defensible since the agent must reproduce that exact wording.

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?

Covers what a multi-step, nested-object tool needs: the sequencing, the conditional gate, what step 1 returns, and what the end user experiences. With no output schema, the description supplies the return-value context itself, and the nested answers object is explained via the field-key reference to enquiry_fields.

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 description coverage is 100%, so the baseline is 3. The description exceeds it by tying answers to field keys sourced from enquiry_fields and by explaining that confirmation is the token returned in step 1, establishing the causal link between the two calls rather than restating the field types.

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 verb and resource ("Submits an enquiry to Taxooor") and immediately disambiguates with two explicit negatives: "NOT a purchase, NOT a guaranteed quote." The title's parenthetical reinforces the two-step nature, so an agent can distinguish this from sibling enquiry_fields/enquiry_describe without opening any schema.

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 a prescriptive when-to-call sequence: Step 1 with answers and consent=true to validate, Step 2 "only if the person agrees" with the same answers plus the confirmation token. It also tells the agent what to do with step 1's output (show the summary and consent line to the person), which is real routing guidance rather than implied usage.

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.

Resources