Skip to main content
Glama

site

by com.whichfieldsoftware

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

submit_enquiry

Submits an enquiry to Which Field Software — 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 field service software vendors, 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 field service software vendors, 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 behavioral burden and does so thoroughly. It discloses the two-step validation/submission behavior, the return values from step 1, the email side effect, the link-click requirement before providers see the enquiry, and the exact consent wording.

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 each sentence earns its place: it front-loads the core purpose and exclusions, then clearly sequences the two steps and consent requirement. The verbatim consent line is included because it is legally/operationally necessary, not 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?

For a multi-step, consent-sensitive, nested-object tool with no annotations and no output schema, the description is remarkably complete. It covers the full call sequence, required parameters, expected step-1 response, user consent handling, email notification, and the provider-visibility condition tied to link click.

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?

Schema coverage is already 100%, but the description adds meaningful semantics beyond the schema: that answers are keyed by field keys from enquiry_fields, that confirmation is the token returned in step 1, and that the same answers plus consent=true must accompany the token in step 2. This links each parameter to a concrete stage of the 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?

The description states a specific action, 'Submits an enquiry to Which Field Software,' and immediately clarifies what it is not ('NOT a purchase, NOT a guaranteed quote'). It clearly distinguishes itself from sibling tools that compare or describe options by framing this as the submission endpoint.

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 gives explicit step-by-step usage conditions: when to make the first call, when to make the second, and that the second call must happen only after the person agrees. It also tells the agent to show the person the summary and consent line, leaving no ambiguity about the required interaction flow.

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

The comparison tools are cleanly separated by role: criteria are the dimensions, options are the entities, and the table is the cross-product. The enquiry tools are also distinct: describe explains the process, fields gives the schema, and submit_enquiry performs the action. There is no meaningful overlap between any pair.

Naming Consistency4/5

The comparison tools follow a consistent compare_ prefix with noun objects, while the enquiry tools are mostly enquiry_ prefixed except for submit_enquiry. This grouping is recognizable but not a single uniform verb_noun pattern across the entire set. The deviation is minor and does not cause confusion.

Tool Count5/5

At six tools, the server is tightly scoped to its two core functions: running a comparison and handling enquiries. Every tool has a distinct purpose and none feel redundant or missing. The count is appropriate for a focused site-specific server.

Completeness5/5

The comparison surface fully covers the domain: criteria, options, and the full results table. The enquiry surface covers the entire lifecycle from describing the process and field schema to the two-step confirmation submission. There are no obvious dead ends or missing operations for the stated functionality.

Resources