Skip to main content
Glama

site

by com.prsicalculator

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

submit_enquiry

Submits an enquiry to PRSI 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 relevant 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 relevant 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?

No annotations provided, so description carries full burden. It discloses validation behavior, return of summary/consent line/token, the email-with-link requirement before provider sees it, and the exact consent statement. This covers the important side effects and flow.

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?

Four dense sentences, front-loaded with purpose and exclusions, then numbered steps and the consent text. No filler; each sentence carries operational meaning.

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?

Given no output schema and no annotations, the description still explains both call steps, expected returns, the email link behavior, and the consent condition. An agent has everything needed to execute the two-step flow correctly.

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?

Despite 100% schema coverage, the description adds meaning: answers must be keyed by field key from enquiry_fields, confirmation is the step-1 token, and consent must be the exact quoted agreement. This goes beyond the schema's generic type 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 verb ('Submits an enquiry'), the target resource ('PRSI Calculator'), and explicitly excludes purchase/quote interpretations. The two-step workflow and reference to enquiry_fields distinguish it from sibling describe/calculate tools.

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 two-step protocol: step 1 call with answers and consent=true, then step 2 after user approval with confirmation token. It also states it is not a purchase or quote and points to enquiry_fields for valid 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

A4/5.0
Disambiguation5/5

Each tool has a distinct role: calculate runs the calculator, calculator_describe explains it, enquiry_describe explains the enquiry process, enquiry_fields provides field metadata, and submit_enquiry performs the two-step submission. There is no meaningful overlap between the tools.

Naming Consistency2/5

Naming conventions are mixed: calculate and submit_enquiry are verb-first, while calculator_describe and enquiry_describe place the noun first and enquiry_fields is a noun phrase. The inconsistency makes the set feel less predictable, though still readable.

Tool Count5/5

Five tools is well-scoped for a single calculator plus enquiry workflow. Each tool earns a place and the count is neither thin nor bloated.

Completeness5/5

The surface covers both major functions: running/explaining the PRSI calculation and describing/submitting an enquiry with all needed metadata and consent flow. There are no obvious dead ends or missing operations within the stated domain.

Resources