Skip to main content
Glama

site

by com.maltaresidencycost

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

submit_enquiry

Submits an enquiry to Malta Residency Cost — 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 relevant Malta residence advisers, who'll quote 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 relevant Malta residence advisers, who'll quote 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 burden. It discloses the two-step validation flow, the requirement for explicit consent, the exact consent wording, the email with a click link, and that providers only see the enquiry after the person clicks the link.

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 longer than typical, but every sentence carries necessary operational information. It is front-loaded with the most important caveat ('NOT a purchase'), then logically sequences Step 1 and Step 2 with no filler.

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?

Despite having no output schema, the description explains what step 1 returns (summary, consent line, confirmation token) and what step 2 results in (submission and a required email link click). For a high-complexity, two-step, consent-gated tool, this is complete enough for an agent to invoke it 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?

Although the schema already documents all three parameters, the description adds essential semantics: answers are keyed by enquiry_fields keys, consent must be true only when the person agrees to the quoted line, and confirmation is the token returned in step 1. This goes well beyond the schema's basic 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?

The description states a specific verb and resource ('Submits an enquiry to Malta Residency Cost') and immediately clarifies what it is not ('NOT a purchase, NOT a guaranteed quote'). It also outlines a distinct two-step submission flow, which clearly separates it from sibling tools like enquiry_describe 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 guidance: call once with answers and consent=true, show the summary and consent line, then call again only if the person agrees, including the confirmation token. It also references enquiry_fields for answer keys, giving the agent a clear path to the correct supporting sibling tool.

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

Each tool has a clear, distinct role: enquiry_describe explains the submission process, enquiry_fields provides the input schema, and submit_enquiry performs the actual submission. There is no meaningful overlap or risk of selecting the wrong tool.

Naming Consistency3/5

All names include 'enquiry' so the domain is clear, but the pattern is mixed: enquiry_describe and enquiry_fields use an enquiry_ prefix, while submit_enquiry puts the verb first. This is readable but not a consistent verb_noun convention.

Tool Count5/5

Three tools is exactly right for this narrow server purpose. Each tool earns its place: one to understand the flow, one to get the fields, and one to submit the enquiry.

Completeness5/5

The server fully covers its stated domain: explaining the enquiry process, enumerating fields, validating, and submitting with consent and confirmation. There are no obvious lifecycle gaps for an enquiry-only tool.

Resources