Skip to main content
Glama

site

by uk.co.contractorpaycalculator

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

submit_enquiry

Submits an enquiry to Contractor Pay 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 specialist contractor accountant, 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 specialist contractor accountant, 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.8/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and covers it thoroughly: validation, summary and token return, email notification, the recipient's pre-submission click requirement, and exact consent wording. It also warns this is not a purchase or guaranteed quote, which prevents mistaken expectations.

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 carries necessary workflow, consent, or exclusion information. Key constraints are front-loaded, and the consent quote is included where it matters.

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, consent-gated submission with no output schema and no annotations, the description is complete: agent knows inputs, sequencing, human-facing consent, token handoff, and what happens after submission. Nothing needed to call it correctly appears missing.

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 coverage is 100%, the description adds workflow meaning: answers must be keyed by enquiry_fields keys, consent must be true and accompanied by the exact consent sentence, and confirmation is the token from step 1 used only after approval. This goes beyond the schema's generic object/boolean/string definitions.

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?

Description begins 'Submits an enquiry to Contractor Pay Calculator' with explicit exclusions 'NOT a purchase, NOT a guaranteed quote', distinguishing it from calculation/purchase tools. The two-step nature is stated up front, so an agent knows exactly what action this tool performs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides a precise step-by-step workflow: call once to validate and obtain a token, then call again only if the person agrees, with same answers and consent=true. It tells the agent when not to call and clarifies provider visibility requires an email click, though it doesn't explicitly name sibling alternatives.

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

Each tool has a distinct role: calculate runs the calculator, calculator_describe documents it, while enquiry_describe explains the enquiry flow, enquiry_fields provides the schema, and submit_enquiry performs the submission. There is no meaningful overlap or ambiguity between them.

Naming Consistency4/5

Names are readable and mostly follow a noun-oriented pattern for descriptive tools (calculator_describe, enquiry_describe, enquiry_fields) with action verbs for operations (calculate, submit_enquiry). The main inconsistency is that calculate is a bare verb while calculator_describe reverses the verb-noun order, but this is minor and not confusing.

Tool Count5/5

Five tools is well-scoped for this server's purpose: two calculator-related tools and three enquiry-related tools. Each tool has a clear place and none feel redundant or missing.

Completeness5/5

The surface fully covers the calculator and enquiry workflow: the calculator can be executed and its assumptions inspected, and the enquiry flow includes process documentation, field schema, and a validated two-step submission with consent. No obvious dead ends or missing operations are apparent.

Resources