Skip to main content
Glama

Submit an ENQUIRY to EPOS system for retail (two steps; not a purchase)

submit_enquiry

Submits an enquiry to EPOS system for retail: 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 EPOS system for retail team sees it. Consent means the person has read and agreed to: "Happy to be contacted about this enquiry by the company that runs this site."

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: Happy to be contacted about this enquiry by the company that runs this site.
confirmationNothe confirmation token from step 1, after the person has approved the summary

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

With zero annotations, the description carries the full burden and does it well: it discloses the validation-and-summary behavior of step 1, the returned confirmation token, the email with a mandatory verification link, and that the team cannot see the enquiry until that link is clicked. It stops short of failure modes: nothing about what happens when validation fails, whether the token expires, or whether step 1 persists any state.

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 critical disambiguation ('NOT a purchase') and then ordered chronologically by step, which matches how the agent must act. It is dense but every sentence carries procedural weight; the only minor redundancy is restating the consent sentence that already appears in the schema's consent description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a nested-object, three-parameter mutation tool with no output schema and no annotations, the description covers the full call lifecycle, side effects, and the shape of what comes back (summary, consent line, token). Error and edge-case behavior (invalid answers, reused token) is the remaining gap, which is a reasonable omission for a submission tool.

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 baseline is 3, but the description adds real meaning beyond the schema: it defines where the answers' keys come from (enquiry_fields), clarifies that consent=true means a specific person-facing statement has been agreed to, and — most importantly — explains that 'confirmation' is the token returned by step 1 and only supplied after approval. That sequencing is not inferable from the field's type alone.

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 (submits), resource (an enquiry to the EPOS system for retail), and explicitly carves out what it is NOT: 'NOT a purchase, NOT a guaranteed quote.' The reference to 'field key from enquiry_fields' also ties it to a named sibling, so an agent can place it in the workflow without opening another 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 when-to-use guidance broken down by step: step 1 with answers + consent=true for validation, step 2 only 'if the person agrees' with the confirmation token. The gating condition (human approval between calls) and the consent prerequisite are both spelled out, leaving nothing 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