Skip to main content
Glama

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

submit_enquiry

Submits an enquiry to Oklahoma Foundation Repair Cost: 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 local foundation repair contractors, chosen by Oklahoma Foundation Repair Cost, 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 local foundation repair contractors, chosen by Oklahoma Foundation Repair Cost, 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 local foundation repair contractors, who'll quote me directly."New value: +"true only when the person has agreed to: Send my contact details to up to three local foundation repair contractors, chosen by Oklahoma Foundation Repair Cost, 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.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 unusually well: it discloses the validation step, what step 1 returns, the double opt-in requirement (email link clicked before any provider sees the data), and the exact scope of consent (up to three contractors, notification per firm, ability to stop further sharing). Gaps remain around failure modes — what happens if validation fails, whether the confirmation token expires, and whether re-invoking step 2 duplicates the enquiry.

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 negations, then a clean step-by-step structure that matches the actual call order. The one inefficiency is the consent paragraph quoted verbatim, which duplicates the consent parameter's schema description word for word.

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, yet the description explains what step 1 returns (summary, consent line, token) and what step 2 produces (submission plus a verification email), which is exactly what an agent needs to drive the conversation. For a no-annotation mutation tool with real-world side effects, this is close to complete.

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 genuinely new meaning: answers are keyed by the field key from enquiry_fields (a cross-tool contract not in the schema), and confirmation is scoped to 'the confirmation token from step 1' issued only after the person approves the summary. It adds sequencing semantics the schema alone does not convey.

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 (submit an enquiry to Oklahoma Foundation Repair Cost) and immediately bounds it with two explicit negations: NOT a purchase, NOT a guaranteed quote. Combined with the two-step framing, an agent can tell this apart from the read-oriented siblings enquiry_fields and enquiry_describe 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 explicit call sequencing: step 1 with answers plus consent=true, then step 2 'only if the person agrees' with the same answers plus the confirmation token. The precondition (human approval of the summary) and the exclusion (do not treat as a purchase/quote) are both stated, leaving little to inference.

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