Skip to main content
Glama
Sign In

site

by uk.co.cardmachinepricing
OverviewDiscussionsAdmin

Submit an ENQUIRY to Card Machine Pricing (two steps; not a purchase)

submit_enquiry

Submits an enquiry to Card Machine Pricing: 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 Card Machine Pricing team sees it. Consent means the person has read and agreed to: "By sending this you agree the Card Machine Pricing 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 Card Machine Pricing 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 Card Machine Pricing passes your details to card machine providers covering your trade."New value: +"true only when the person has agreed to: By sending this you agree the Card Machine Pricing team reads your enquiry and replies by email. We do not pass it to anyone else."
  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 validate-then-submit flow, the returned confirmation token, the email double opt-in before the team sees the enquiry, the exact consent wording, and explicit negations about purchase and quote. This is substantially more than the schema conveys.

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?

The Step 1 / Step 2 structure is well front-loaded and easy to follow. Some text is redundant — the consent sentence is reproduced almost verbatim in the consent parameter description — but the overall length is justified by the two-step protocol.

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?

Despite no output schema, the description states what step 1 returns (summary, consent line, confirmation token) and what step 2 produces (submission plus a verification email). For a nested-object, multi-step mutation tool, nothing an agent needs to call it correctly 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 description coverage is 100%, so the baseline is 3; the description still adds the sequencing meaning of 'confirmation' (only after approval, same answers re-sent) and the source of answer keys. It stops short of describing value formats for individual answers, leaving some interpretation to the schema.

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 specific verb and resource ('Submits an enquiry to Card Machine Pricing') and immediately bounds scope with 'NOT a purchase, NOT a guaranteed quote'. It also names the sibling that supplies the field keys ('keyed by field key from enquiry_fields'), so an agent can tell this apart from the read-only enquiry/dataset tools.

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?

Usage is spelled out as an explicit two-step protocol: step 1 with answers and consent=true, then step 2 'only if the person agrees' with the same answers plus the confirmation token. The prerequisite for advancing (human approval of the summary) is stated rather than inferred, and the alternative path (enquiry_fields for keys) is named.

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