Skip to main content
Glama

site

by com.pdoccalculator

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

submit_enquiry

Submits an enquiry to Employer CPP EI Calculator — 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 Canadian payroll providers, 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 Canadian payroll providers, 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

A4.9/5.0
Behavior5/5

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

With no annotations, the description fully carries behavioral disclosure. It reveals that this is neither a purchase nor a guaranteed quote, requires explicit consent with the exact consent wording, returns a summary and confirmation token, and that the enquiry is only delivered after the recipient clicks an emailed link. This is comprehensive behavioral context.

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 dense but well organized into numbered steps with clear conditions. Key disclaimers are front-loaded, and every sentence contributes operational or semantic value. The length is justified by the two-step workflow and consent requirements.

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?

Despite having no output schema, the description explains what step 1 returns (summary, consent line, confirmation token) and what step 2 triggers (submission and email link). Combined with the detailed parameter descriptions and explicit workflow, an agent has everything needed to invoke the tool correctly in both steps.

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 schema already documents parameters well. The description still adds value by specifying that answers are keyed by field key from enquiry_fields, that consent must be true, and that the confirmation token comes from step 1 and must accompany the same answers in step 2. This goes beyond the schema's basic property descriptions.

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 action (submits an enquiry), the target (human providers via Employer CPP EI Calculator), and explicitly distinguishes itself from a purchase or quote. The two-step nature is conveyed in the title and description, making it easy to separate from sibling tools like calculate.

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?

Provides an explicit, step-by-step invocation protocol: step 1 requires answers and consent=true, returns a token; step 2 requires the same answers plus the token only after the person agrees. It also clarifies the condition for calling the tool again and the consent requirement, leaving no ambiguity about when to use it.

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

A4/5.0
Disambiguation4/5

Most tools have clearly distinct roles: run the calculator, describe the calculator, describe the enquiry process, list enquiry fields, and submit the enquiry. The only mild ambiguity is between enquiry_describe and enquiry_fields, though their descriptions do separate high-level process from field schema.

Naming Consistency3/5

The names mix conventions: 'submit_enquiry' and 'calculate' use verb-first style, while 'calculator_describe', 'enquiry_describe', and 'enquiry_fields' are noun-first. The names are still readable and intuitive, but the pattern is not consistent.

Tool Count5/5

Five tools is well-scoped for this narrow calculator-plus-enquiry workflow. Each tool has a distinct purpose and the count feels neither bloated nor thin.

Completeness5/5

The tool set covers the full workflow: understanding the calculator, running it, understanding the enquiry flow, retrieving required fields, and submitting the enquiry with confirmation handling. There are no obvious dead ends for an agent helping a user complete this process.

Resources