Skip to main content
Glama

site

by nz.co.finalpaycalculator

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

submit_enquiry

Submits an enquiry to Final Pay 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: "Happy for my details to go to an employment adviser or payroll specialist, who'll contact me directly."

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
answersYesthe person's answers, keyed by field key
consentYestrue only when the person has agreed to: Happy for my details to go to an employment adviser or payroll specialist, who'll contact me directly.
confirmationNothe confirmation token from step 1, after the person has approved the summary

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A5/5.0
Behavior5/5

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

No annotations are present, so the description carries full disclosure. It reveals side effects (email sent with a link), gating (provider sees nothing until the link is clicked), consent semantics, and the fact that the first call does not submit.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but every sentence earns its place; the key warnings are front-loaded and the two-step flow is clearly structured. The consent quote is verbose but essential.

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-step submission tool with no output schema and no annotations, the description covers the full calling sequence, expected return values, success behavior, and post-submission requirement. An agent can call it correctly without additional information.

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

Parameters5/5

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

Schema coverage is 100%, but the description adds critical meaning beyond it: answers must be keyed by enquiry_fields keys, consent must match the exact quoted statement, and confirmation is the token returned in step 1. This is exactly the operational context an agent needs.

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 an enquiry'), a specific resource ('Final Pay Calculator NZ'), and immediately clarifies it is not a purchase or a guaranteed quote. This clearly separates the tool from calculator and description siblings.

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?

The description gives explicit two-step invocation instructions: call once with answers and consent to get a token, then call again only if the person agrees. It also states when not to proceed and points to enquiry_fields for the correct answer keys.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation5/5

Each tool has a clearly distinct role: calculate runs the calculator, calculator_describe explains its inputs and assumptions, enquiry_describe explains the enquiry process, enquiry_fields provides the schema, and submit_enquiry handles the two-step submission. There is no meaningful overlap or ambiguity.

Naming Consistency3/5

Names are readable but follow mixed conventions: calculate is a bare verb, calculator_describe and enquiry_describe are noun-verb, enquiry_fields is noun-noun, and submit_enquiry is verb-noun. The pattern is not chaotic but it is not consistent.

Tool Count5/5

Five tools is well-scoped for a focused NZ final pay calculator and enquiry submission domain. Each tool serves a necessary part of the workflow without bloat or redundancy.

Completeness5/5

The tool surface covers calculator execution, calculator metadata, enquiry process explanation, field definitions, and the full two-step enquiry submission flow. There are no obvious dead ends or missing operations for the stated purpose.

Resources