Skip to main content
Glama

Submit an ENQUIRY to Bags That Pay (two steps; not a purchase)

submit_enquiry

Submits an enquiry to Bags That Pay: 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 Bags That Pay team sees it. Consent means the person has read and agreed to: "By sending this you agree the Bags That Pay 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 Bags That Pay 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 Bags That Pay passes your question to the issuer or data provider you asked about."New value: +"true only when the person has agreed to: By sending this you agree the Bags That Pay team reads your enquiry and replies by email. We do not pass it to anyone else."
  2. First observed

TDQS

A4.6/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 validation behavior, what step 1 returns (summary, consent line, confirmation token), the double opt-in email flow where the person must click a link before the team sees it, and the exact consent wording. That is rich behavioral context beyond anything structured.

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 crucial negation and cleanly organized as Step 1 / Step 2, so the structure is easy to follow. Minor waste: the consent sentence is quoted verbatim even though the schema already repeats it.

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?

There is no output schema, and the description compensates fully by describing both the step-1 return payload and the final email-with-link outcome. Nothing an agent needs to drive the two-step flow 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 coverage is 100%, so the baseline is 3, but the description adds real meaning: answers are keyed by field key sourced from enquiry_fields, consent is only true after the person has read the quoted statement, and confirmation is the token returned by step 1 used only on the second call. The step sequencing of confirmation is meaningful beyond the schema's one-line description.

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 Bags That Pay') and immediately fences it off from the payment siblings with 'NOT a purchase, NOT a guaranteed quote'. An agent can tell this apart from listing_pay_* tools 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit two-step protocol with the condition that gates step 2 ('only if the person agrees') and the exact inputs for each step. It does not name a sibling alternative by name, but the 'not a purchase' framing plus the enquiry_fields reference routes the agent adequately.

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