Skip to main content
Glama

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

submit_enquiry

Submits an enquiry to Notice Period Calculator NZ: 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 Notice Period Calculator NZ, 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 Notice Period Calculator NZ, 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 relevant employment lawyers or workplace advisers, chosen by Notice Period Calculator NZ, 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 Notice Period Calculator NZ, 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 a relevant employment lawyer or workplace adviser, who'll contact me directly."New value: +"true only when the person has agreed to: Send my contact details to up to three relevant employment lawyers or workplace advisers, chosen by Notice Period Calculator NZ, 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.6/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so: it discloses validation, the returned summary/consent line/token, that submission is deferred to a second call, that an emailed confirmation link must be clicked before any provider sees the data, and that details go to up to three named providers. It also spells out exactly what 'consent' means, which is the highest-risk behavioral detail for this 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 disclaimers, then the two steps in order, which is the right structure for a multi-call flow. The cost is a long single paragraph and a verbatim repeat of the consent sentence that already appears in the schema, which is defensible for self-containment but adds bulk.

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 stating what step 1 returns (summary, consent line, confirmation token) and what the submission triggers downstream (a verification email before provider visibility). For a nested-object, consent-gated mutation, an agent has everything needed to call it correctly and safely.

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 coverage is 100% and already documents all three parameters, including the full consent text and the token's origin, so the baseline is 3. The description adds useful sequencing context (answers keyed by field key from enquiry_fields, token coming from step 1) but nothing about types or formatting that the schema lacks.

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?

Opens with a specific verb+resource ('Submits an enquiry to Notice Period Calculator NZ') and immediately fences off the two most likely misreadings ('NOT a purchase, NOT a guaranteed quote'). That framing plus the reference to enquiry_fields lets an agent separate this from the calculate/describe siblings without opening a 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-call protocol with the gating condition spelled out: step 1 with answers+consent=true, step 2 'only if the person agrees' with the token. It also states what must be shown to the person between the steps, so the agent knows the sequencing is mandatory rather than optional.

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