Skip to main content
Glama
Sign In

site

by com.payrollservicesquotes
OverviewDiscussionsAdmin

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

submit_enquiry

Submits an enquiry to Payroll Services Quotes: 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: "By sending this you agree the Payroll Services Quotes 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 Payroll Services Quotes 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 Payroll Services Quotes shares your details with payroll and PEO providers who may contact you."New value: +"true only when the person has agreed to: By sending this you agree the Payroll Services Quotes team reads your enquiry and replies by email. We do not pass it to anyone else."
  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 so well: it discloses that step 1 only validates and returns a summary/consent line/token, that nothing reaches providers until the person clicks an emailed link, and the exact scope of what consent authorizes. Minor gaps remain around failure behavior (what happens when validation rejects the answers) and whether an enquiry can be withdrawn or re-submitted.

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?

The most decision-relevant fact is front-loaded ('NOT a purchase'), and the two steps are clearly enumerated. It is dense but readable; the only waste is near-verbatim repetition of the consent sentence already present in the consent parameter schema, which lengthens the block without adding new information.

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 two-phase, nested-object, no-output-schema tool this is appropriately complete: it explains what each phase returns, how the phase handoff token works, and the downstream email confirmation gate. Nothing an agent needs in order to call it correctly in either phase 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 beyond it: answers must be 'keyed by field key from enquiry_fields' (cross-tool linkage), consent must be 'true', and confirmation is specifically 'the confirmation token from step 1, after the person has approved the summary'. That token lifecycle is not obvious from the schema 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?

Names a specific verb and resource ('Submits an enquiry to Payroll Services Quotes') and immediately bounds it with 'NOT a purchase, NOT a guaranteed quote'. That distinction is exactly what separates it from the sibling lookup tools (enquiry_fields, enquiry_describe) an agent might otherwise reach for.

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 sequenced when-to-use: step 1 with answers plus consent=true to validate, step 2 'only if the person agrees' with the added token. It also names the gating condition (human agreement) and states the consent precondition in full, leaving no inference about ordering.

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