Skip to main content
Glama
Sign In

site

by uk.co.currentannuityrates
OverviewDiscussionsAdmin

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

submit_enquiry

Submits an enquiry to Current Annuity Rates — 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: "Send my contact details to up to three annuity specialists, chosen by Current Annuity Rates, who'll contact me directly. I'll be emailed each firm's name as my details go to it, and can stop any more firms getting them."

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: Send my contact details to up to three annuity specialists, chosen by Current Annuity Rates, who'll contact me directly. I'll be emailed each firm's name as my details go to it, and can stop any more firms getting them.
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: Happy for my details to go to an annuity specialist, who'll contact me directly."New value: +"true only when the person has agreed to: Send my contact details to up to three annuity specialists, chosen by Current Annuity Rates, who'll contact me directly. I'll be emailed each firm's name as my details go to it, and can stop any more firms getting them."
  2. First observed

TDQS

A4.8/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 and does so: it discloses the two-phase validation flow, what Step 1 returns (summary, consent line, token), the hard requirement that the person click an emailed link before any provider sees the data, and the exact scope of data sharing (up to three specialists, chosen by the vendor, with per-firm notification and opt-out). The 'show the person the summary and the consent line' instruction is behavior the agent could not infer from schema or annotations.

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 purpose and the critical 'not a purchase' caveat, then proceeds in clean Step 1 / Step 2 order. It is long, but the length is justified by a genuinely two-phase protocol; the one redundancy is the consent string, which is repeated verbatim from the consent parameter's schema description.

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 nested-object, multi-step submission tool with no output schema and no annotations, the description covers everything an agent needs: call sequence, required flags per call, what gets returned at each step, and the downstream consequences for the person. Return values are described inline, so the absence of an output schema is not a gap.

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 and the schema already documents all three parameters. The description adds meaning beyond it by explaining that answers are keyed by field key from enquiry_fields, that consent must be literally true, and that confirmation is the token returned by Step 1 and is only passed on the second call. That sequencing context is real added value, though the consent text itself is verbatim duplication.

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 Current Annuity Rates') and immediately delimits what it is not ('NOT a purchase, NOT a guaranteed quote'), which is the exact confusion an agent would have with the calculate/calculator_describe siblings. It also names the enquiry_fields sibling as the source of field keys, so the agent can route between tools without opening schemas.

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 sequencing: Step 1 with answers+consent=true, then Step 2 only if the person agrees, with the token. It also states the exclusion (not a purchase, not a guaranteed quote) so the agent won't use it for transactional intent. Nothing about when to proceed is left to inference.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources