Skip to main content
Glama

site

by uk.bankconvert

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

submit_enquiry

Submits an enquiry to Bank Convert — 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 bookkeeping and data extraction suppliers, 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 bookkeeping and data extraction suppliers, 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.7/5.0
Behavior5/5

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

With no annotations, the description fully carries the behavioral disclosure burden. It reveals the two-step validation behavior, the confirmation token requirement, the email with a link, the condition that providers see the enquiry only after the link is clicked, and the exact consent text. This is exemplary transparency.

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 dense but every sentence provides essential operational detail. It front-loads the key caveat ('NOT a purchase, NOT a guaranteed quote'), then structures the two steps clearly. No filler or redundancy is present.

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?

For a two-step submission tool with no output schema and no annotations, the description is remarkably complete. It explains what happens at each step, what the agent must show the person, when to proceed to step 2, and what the person must do before providers see the enquiry. 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 100%, so the baseline is 3. The description adds meaningful semantics beyond the schema: answers must be keyed by field key from enquiry_fields, consent=true is a precondition in both steps, and the confirmation token comes from step 1 and is required for final submission. This elevates the score above baseline.

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 clearly states the tool submits an enquiry to human providers and explicitly distinguishes it from a purchase or guaranteed quote. The two-step process is laid out in concrete terms, making the purpose unmistakable and distinct from sibling tools like compare_options or enquiry_describe.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit procedural usage guidance: call once with answers and consent, show the summary and consent line, then call again with the confirmation token only if the person agrees. It does not explicitly name alternatives, but the step-by-step workflow and the 'NOT a purchase' framing provide clear context for when this tool is appropriate.

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

B3.4/5.0
Disambiguation4/5

The compare_* tools separate criteria, option metadata, and the full option-by-criterion table, so an agent can choose the right level of detail. The enquiry_* tools are also distinct: describe explains the process, fields provides the schema, and submit_enquiry performs the submission. There is slight potential overlap because compare_table contains the data that the other two compare tools also expose, but the descriptions make the boundaries clear enough.

Naming Consistency3/5

All tool names use lowercase snake_case and the compare_* and enquiry_* prefixes provide some structure. However, the pattern is mixed: compare_criteria, compare_options, and compare_table are verb-first, while enquiry_describe and enquiry_fields are noun-first, and submit_enquiry is verb-first again. The names are readable but do not follow one predictable convention.

Tool Count5/5

Six tools is a well-scoped size for this server. Each tool serves a clear purpose within the comparison and enquiry workflows, and there is no sense of bloat or thinness.

Completeness5/5

The comparison surface is complete: criteria, option metadata, and the full comparison table are all available. The enquiry workflow is also complete, covering the process description, field schema, and a two-step consent-based submission with confirmation token.

Resources