Skip to main content
Glama

site

by com.canadapayrollcalculator

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

submit_enquiry

Submits an enquiry to Canada Payroll 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 a Canadian accountant or payroll provider, 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 a Canadian accountant or payroll provider, 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?

With no annotations provided, the description fully carries the behavioral disclosure burden. It reveals the two-step validation/submission flow, the consent requirement with the exact consent text, the email with a click-link before providers see data, and the non-guaranteed nature of the quote. All side effects and preconditions are explicitly disclosed.

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 every sentence earns its place. The 'NOT a purchase' disclaimer is front-loaded, the steps are clearly labeled, and there is no filler or repetition. The length is justified by the complexity of the two-step workflow.

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, side-effectful tool with no output schema and no annotations, the description covers everything an agent needs to invoke it correctly: preconditions, consent text, step sequence, token handoff, and post-submission behavior. It also points to enquiry_fields for the answer keys, making the context complete.

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?

Although schema descriptions cover 100% of parameters, the description adds significant meaning: answers must be keyed by field keys from enquiry_fields, consent requires the exact quoted agreement, and confirmation is the token returned from step 1. This ties each parameter to its procedural role, going well beyond the baseline schema coverage.

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?

The description states a specific verb ('Submits an enquiry') and resource ('Canada Payroll Calculator'), and immediately distinguishes it from a purchase or guaranteed quote. The two-step process and explicit 'NOT a purchase' clearly separate it from siblings like calculate and enquiry_fields.

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 provides explicit step-by-step usage: Step 1 with answers and consent=true, then Step 2 with the confirmation token only if the person agrees. It also references enquiry_fields for answer keys and states exclusions ('NOT a purchase, NOT a guaranteed quote'), giving clear when-to-use and when-not-to-use guidance.

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.2/5.0
Disambiguation5/5

Each tool has a clear single responsibility: calculate runs the calculator, calculator_describe explains it, enquiry_describe explains the submission flow, enquiry_fields provides the schema, and submit_enquiry does the actual submission. There is no meaningful overlap between the calculator cluster and the enquiry cluster.

Naming Consistency3/5

Names are readable and all snake_case, but the pattern is mixed: calculate and submit_enquiry are verb-first while calculator_describe, enquiry_describe, and enquiry_fields are noun-first/noun-noun. The two describe tools are consistent with each other, but the set as a whole lacks a single predictable verb_noun convention.

Tool Count5/5

Five tools is well-scoped for a server that provides a payroll calculator and an enquiry submission flow. Each tool covers a distinct function, and there is no bloat or token-heavy sprawl.

Completeness5/5

The calculator surface has both run and self-description, and the enquiry surface has process description, field schema, and a two-step submit flow with explicit consent handling. No critical lifecycle gap is obvious for this narrow domain.

Resources