Skip to main content
Glama

site

by com.boatvaluecalculator

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

submit_enquiry

Submits an enquiry to Boat Value 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: "Happy for my details to go to a marine surveyor or broker, 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 marine surveyor or broker, 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

A5/5.0
Behavior5/5

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

With no annotations provided, the description carries the full disclosure burden and does so richly: it reveals the two-step validation flow, the confirmation token, the email link requirement, and the precise consent statement. It also clearly states that the enquiry is not a purchase and not a guaranteed quote, preventing misinterpretation.

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 long but every sentence earns its place, front-loading the critical caveats ('NOT a purchase, NOT a guaranteed quote') before the step-by-step flow. The two-step structure is logically ordered and avoids redundancy.

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 lacking an output schema and annotations, the description provides the full call sequence, required consent behavior, confirmation token semantics, and post-submission email requirement. Nothing an agent needs to correctly invoke this multi-step tool is missing.

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 parameters, the description adds essential meaning: answers are 'keyed by field key from enquiry_fields', consent must be true with the exact consent wording, and confirmation is the token returned from Step 1. These cross-references make parameter usage actionable 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 action—'Submits an enquiry to Boat Value Calculator'—and clearly distinguishes itself from a purchase or guaranteed quote. It also names invitation-only follow-up steps, making its purpose unmistakable among sibling tools like calculate 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 when-to-use guidance by breaking the operation into Step 1 and Step 2, including the exact condition for proceeding ('only if the person agrees'). It also gives the needed inputs and the meaning of consent, so the agent knows exactly 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

A3.8/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: calculate runs the valuation, calculator_describe and enquiry_describe explain behavior, enquiry_fields provides the schema, and submit_enquiry performs the actual submission. There is no meaningful overlap between the describe tools because one covers the calculator and the other covers the enquiry workflow.

Naming Consistency2/5

Tool names follow mixed patterns: calculate is a bare verb, submit_enquiry is verb_noun, calculator_describe and enquiry_describe are noun_verb, and enquiry_fields is noun_noun. The names are readable but there is no consistent naming convention across the set.

Tool Count5/5

Five tools is a well-sized surface for a calculator-plus-enquiry server. Each tool earns its place and there are no redundant or filler tools.

Completeness5/5

The server fully covers the calculator workflow (run, understand inputs/outputs) and the enquiry workflow (understand behavior, get fields, submit with explicit consent confirmation). No significant gaps are apparent for the stated purpose.

Resources