Skip to main content
Glama

site

by com.maltataxrefundcalculator
OverviewDiscussionsAdmin

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

submit_enquiry

Submits an enquiry to Malta Tax Refund 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: "Send my contact details to up to three relevant Maltese tax practitioners or corporate service providers authorised by the MFSA, chosen by Malta Tax Refund Calculator, who'll contact me directly. I'll be emailed each firm's name as my details go to it, and can stop any more firms getting them."

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
answersYesthe person's answers, keyed by field key
consentYestrue only when the person has agreed to: Send my contact details to up to three relevant Maltese tax practitioners or corporate service providers authorised by the MFSA, chosen by Malta Tax Refund Calculator, who'll contact me directly. I'll be emailed each firm's name as my details go to it, and can stop any more firms getting them.
confirmationNothe confirmation token from step 1, after the person has approved the summary

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / consent / description
      Previous value: -"true only when the person has agreed to: Happy for my details to go to a relevant Maltese tax practitioner or corporate service provider, who'll contact me directly."New value: +"true only when the person has agreed to: Send my contact details to up to three relevant Maltese tax practitioners or corporate service providers authorised by the MFSA, chosen by Malta Tax Refund Calculator, who'll contact me directly. I'll be emailed each firm's name as my details go to it, and can stop any more firms getting them."
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and discloses validation on step 1, the returned summary/consent line/token, and the downstream effects of step 2: submission and an email link the person must click before any provider sees the enquiry. It omits edge cases such as validation failure behavior, but covers the essential process and consent implications well.

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

Conciseness4/5

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

The description is front-loaded with purpose and warnings, then structured into step 1 and step 2. It is somewhat long because it repeats the full consent text already present in the schema, but that repetition is arguably useful for displaying the consent line to the person.

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 annotations, no output schema, and a high schema coverage of 100%, the description is complete enough for an agent to invoke this tool correctly: it explains the two-step flow, consent, confirmation token, and the downstream email-gated submission. Nothing essential for correct invocation appears to be missing.

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 baseline is 3. The description adds meaningful process semantics beyond the schema by explaining that answers are keyed by field key from enquiry_fields, that consent=true is needed in both steps, and that the confirmation token is only for step 2.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific verb and resource: 'Submits an enquiry to Malta Tax Refund Calculator', and immediately distinguishes it from a purchase or guaranteed quote. It does not compare against sibling tools like calculate or enquiry_describe, so it stops short of full sibling differentiation.

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?

It gives an explicit two-step workflow: step 1 call with answers and consent=true, show the summary and consent line, then step 2 call again with the same answers, consent=true, and the confirmation token only if the person agrees. It also specifies the critical when-not condition ('NOT a purchase, NOT a guaranteed quote') and references enquiry_fields for 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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources