Skip to main content
Glama

Submit an ENQUIRY to Capital Gains Tax HQ (two steps; not a purchase)

submit_enquiry

Submits an enquiry to Capital Gains Tax HQ: 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 Capital Gains Tax HQ team sees it. Consent means the person has read and agreed to: "By sending this you agree the Capital Gains Tax HQ team reads your enquiry and replies by email. We do not pass it to anyone else."

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 sending this you agree the Capital Gains Tax HQ team reads your enquiry and replies by email. We do not pass it to anyone else.
confirmationNothe confirmation token from step 1, after the person has approved the summary

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / consent / description
      Previous value: -"true only when the person has agreed to: By submitting you agree Capital Gains Tax HQ shares your question with tax advisers who may reply with a written answer and a fee."New value: +"true only when the person has agreed to: By sending this you agree the Capital Gains Tax HQ team reads your enquiry and replies by email. We do not pass it to anyone else."
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does so well: it discloses that step 1 is a validation-only call returning a summary, consent line and token, and that step 2 triggers an email with a link the person must click before the HQ team sees the enquiry. Remaining gaps are error/retry behavior and whether step 1 may be re-run after a rejection, which is why this is a 4 rather than a 5.

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?

Densely front-loaded with the purpose and the negative framing before the procedural steps, and every sentence carries operational content. Minor deduction because the full consent sentence is reproduced in the description and again in the schema's consent property, costing length without adding new information.

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 two-phase mutation with no annotations and no output schema, the description covers everything an agent needs: the step order, what step 1 returns, the human approval gate, the double opt-in email side effect, and the exact scope of consent. Nothing essential about correct invocation is left unstated.

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, but the description adds real meaning: answers are keyed by field keys obtained from enquiry_fields, consent encodes a specific disclosed consent statement, and confirmation is a token that only exists after step 1 approval. That clarifies the lifecycle of each parameter beyond the schema's field-level text.

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 Capital Gains Tax HQ") and immediately rules out the two most likely misreadings ("NOT a purchase, NOT a guaranteed quote"). It also names the sibling source of field keys (enquiry_fields), so an agent can tell this apart from the field-listing tool without opening either 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 an explicit two-step protocol: step 1 with answers + consent=true to validate and obtain a token, step 2 only after the person agrees, with the same answers plus the token. Both the when-to-call and the precondition for advancing are stated, and the human-in-the-loop gate is unambiguous.

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