Skip to main content
Glama

site

by uk.co.fsmacrypto

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

submit_enquiry

Submits an enquiry to FSMA Crypto Promotions Checker — 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 financial promotions compliance specialist, 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 financial promotions compliance specialist, 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 provided, the description carries full disclosure burden and does so thoroughly: validation on the first call, return of a summary/consent line/token, the second-call submission, and an email link the person must click before any provider sees the enquiry. It also defines consent precisely.

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 long but every clause earns its place because the tool has a genuinely stateful two-step contract. It is front-loaded with the most important disambiguation ('NOT a purchase'), and the step-by-step structure is easy for an agent to parse.

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 adequately explains what the tool returns step by step, what the person receives, and the prerequisite consent behavior. It also points the agent to enquiry_fields for the answer keys, so nothing critical is 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 already 100%, but the description adds essential meaning beyond the schema: it explains that answers are keyed by field key from enquiry_fields, that consent must be true, and that the confirmation token comes from step 1 and is used in step 2. This turns the parameters from a list into a workflow.

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 action and resource: 'Submits an enquiry to FSMA Crypto Promotions Checker', and immediately disambiguates with 'NOT a purchase, NOT a guaranteed quote.' It also names the two-step nature, which clearly separates it from siblings like enquiry_describe and enquiry_fields that only describe the form.

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 explicit, sequential instructions: call first with the answers and consent=true to obtain a token, then call again with the same answers plus the token only if the person agrees. It also states the consent condition and the email-link requirement, leaving no ambiguity about when and how to invoke the 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/5.0
Disambiguation5/5

Each tool has a clearly distinct role: checker_start, checker_answer, and checker_tree cover different aspects of the decision guide (initial step, stepwise traversal, full map), while enquiry_describe, enquiry_fields, and submit_enquiry cover the enquiry flow (overview, schema, submission). Even the two checker tools that both deal with questions are clearly separated as interactive navigation vs. complete reasoning tree.

Naming Consistency4/5

All names use lowercase snake_case and are grouped by domain prefix (checker_ and enquiry_), which makes them easy to navigate. However, action placement is not fully uniform: checker_answer and enquiry_describe are noun-verb, while submit_enquiry is verb-noun, and checker_tree/enquiry_fields are noun-noun.

Tool Count5/5

Six tools is well-scoped for the server's stated purpose: three tools for the interactive decision guide and three for the enquiry submission flow. Each tool earns its place, with no redundant or missing high-level operations.

Completeness5/5

The surface fully covers both workflows: navigating the decision guide from start to verdict, viewing the full guide structure, and submitting an enquiry with fields, consent, and confirmation tokens. No obvious dead ends or missing lifecycle operations are apparent.

Resources