Skip to main content
Glama

site

by com.maltavatregistration
OverviewDiscussionsAdmin

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

submit_enquiry

Submits an enquiry to Malta VAT Registration — 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 Malta corporate service providers authorised by the MFSA, chosen by Malta VAT Registration, 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 Malta corporate service providers authorised by the MFSA, chosen by Malta VAT Registration, 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: Send my contact details to up to three relevant Maltese VAT practitioners or accountants authorised by the MFSA, chosen by Malta VAT Registration, 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."New value: +"true only when the person has agreed to: Send my contact details to up to three Malta corporate service providers authorised by the MFSA, chosen by Malta VAT Registration, 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. 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 VAT practitioner or accountant, 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 VAT practitioners or accountants authorised by the MFSA, chosen by Malta VAT Registration, 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."
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

No annotations are provided, so the description carries the full behavioral burden and does so thoroughly: it discloses validation behavior, the exact return contents of step 1 (summary, consent line, token), the email-verification requirement before any provider sees the data, and the downstream consequence (contact details sent to up to three MFSA-authorised providers with opt-out rights).

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?

Front-loaded with the highest-value disambiguation ('NOT a purchase') and organized as Step 1 / Step 2. It is long, and the full consent sentence is duplicated between the description and the consent parameter's own schema description, which is somewhat redundant, but the structure remains scannable and each element serves the flow.

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?

With no output schema, the description must describe returns, and it does: step 1 yields a summary, a consent line and a token; step 2 triggers an email with a verification link. Given the nested 'answers' object and the two-phase flow, an agent has everything needed to call this correctly.

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, but the description adds real meaning: it links 'answers' to the field keys produced by the sibling tool enquiry_fields and explains that 'confirmation' is the token returned by step 1 and must only be sent after approval, which is step-ordering context the schema alone does not convey.

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 and resource ('Submits an enquiry to Malta VAT Registration') and immediately disambiguates the most likely misinterpretation with 'NOT a purchase, NOT a guaranteed quote.' An agent can distinguish it from siblings like enquiry_fields and enquiry_describe, which gather/describe data rather than submit it.

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?

Explicitly lays out the two-step protocol: step 1 with answers + consent=true, then step 2 only if the person agrees, with the confirmation token. The gating condition for the second call is stated outright, leaving nothing to inference.

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