Skip to main content
Glama

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

submit_enquiry

Submits an enquiry to Shift Pattern Generator: 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 payroll and HR service providers, chosen by Shift Pattern Generator, 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 payroll and HR service providers, chosen by Shift Pattern Generator, 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: Send my contact details to up to three rota and workforce scheduling suppliers, chosen by Shift Pattern Generator, 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."New value: +"true only when the person has agreed to: Send my contact details to up to three payroll and HR service providers, chosen by Shift Pattern Generator, 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. 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 rota and workforce scheduling suppliers, who'll contact me directly."New value: +"true only when the person has agreed to: Send my contact details to up to three rota and workforce scheduling suppliers, chosen by Shift Pattern Generator, 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."
  3. First observed

TDQS

A4.4/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 behavioral burden and discloses validation, returned summary/consent line/token, the second-call submission gate, email-link verification before any provider sees the enquiry, and the exact consent consequences including up to three providers and stopping future firms. It also clarifies that this is not a purchase or guaranteed quote. Error and token-expiry behavior are not covered, but the key side effects and gating conditions are explicit.

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-loads the core warning and organizes the workflow into clear step 1 and step 2 instructions. However, it repeats the full consent text already present in the schema and repeats 'not a purchase' from the title, so some length is redundant.

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 complex two-step, consent-based submission with no annotations or output schema, the description supplies the return values, consent gate, email verification, and provider-sharing consequences. Remaining gaps around error handling and token lifetime are minor for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents answers, consent, and confirmation. The description adds that answers are keyed by field key from enquiry_fields and that step 2 uses the same answers plus the token, but it largely restates schema-level semantics for consent and confirmation.

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 Shift Pattern Generator', with explicit boundaries 'NOT a purchase, NOT a guaranteed quote'. This lets an agent distinguish it from transaction or quote tools without opening the 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?

Provides an explicit two-step call sequence: step 1 with answers and consent, show the person the summary, then step 2 only after the person agrees, using the confirmation token. It references enquiry_fields for field keys, but does not explicitly compare itself with other sibling tools or state when not to use it versus calculate/describe.

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