Skip to main content
Glama

site

by uk.co.shiftpatterngenerator
OverviewDiscussionsAdmin

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."

Input Schema

TableJSON 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.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 that nothing is submitted until step 2, that a confirmation token is required, that the person must click an email link before any provider sees the data, and spells out the exact consent scope. This is unusually rich behavioral disclosure for a mutation-style tool.

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 key disambiguation, then a clean step-by-step. The only waste is the full consent string repeated verbatim from the schema's consent description, which inflates length without adding meaning.

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 by describing the step-1 return (summary, consent line, confirmation token) and the post-submission side effect (email link gating provider visibility). An agent has everything needed to drive both calls correctly.

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 sequencing semantics beyond the schema: 'answers' must be keyed by field key from the enquiry_fields sibling, and 'confirmation' is only supplied on the second call after approval. That flow context is genuine added value, though the consent text is duplicated verbatim.

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') and immediately disambiguates with 'NOT a purchase, NOT a guaranteed quote', which separates it from the calculator/description siblings. An agent can tell exactly what this does 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 Guidelines5/5

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

Gives an explicit two-step protocol: step 1 with answers+consent to get a token, step 2 only 'if the person agrees' with the token added. It states the gating condition and the prerequisite, 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.

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