Skip to main content
Glama

site

by uk.co.agriculturalbuildingcost
OverviewDiscussionsAdmin

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

submit_enquiry

Submits an enquiry to Agricultural Building 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: "Send my contact details to up to three agricultural building and grain store firms, chosen by Agricultural Building Cost, who'll contact me directly. I'll be emailed each firm's name as my details go to it, and can stop any more firms getting them."

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
answersYesthe person's answers, keyed by field key
consentYestrue only when the person has agreed to: Send my contact details to up to three agricultural building and grain store firms, chosen by Agricultural Building Cost, who'll contact me directly. I'll be emailed each firm's name as my details go to it, and can stop any more firms getting them.
confirmationNothe confirmation token from step 1, after the person has approved the summary

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / consent / description
      Previous value: -"true only when the person has agreed to: Send my contact details to up to three relevant agricultural building contractors, chosen by Agricultural Building Cost, who'll contact me directly. I'll be emailed each firm's name as my details go to it, and can stop any more firms getting them."New value: +"true only when the person has agreed to: Send my contact details to up to three agricultural building and grain store firms, chosen by Agricultural Building Cost, who'll contact me directly. I'll be emailed each firm's name as my details go to it, and can stop any more firms getting them."
  2. Changed1 schema field changed
    • changedInput schema / properties / consent / description
      Previous value: -"true only when the person has agreed to: Happy for my details to go to relevant agricultural building contractors, who'll quote me directly."New value: +"true only when the person has agreed to: Send my contact details to up to three relevant agricultural building contractors, chosen by Agricultural Building Cost, who'll contact me directly. I'll be emailed each firm's name as my details go to it, and can stop any more firms getting them."
  3. 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, the description carries the full burden and does so: it discloses the validate-then-summarize behavior of step 1, the returned artifacts (summary, consent line, confirmation token), the email-plus-click gate before any provider sees the enquiry, and the exact scope of consent (up to three firms, name disclosure, opt-out).

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?

Front-loaded with the critical caveat, then organized as Step 1 / Step 2 / consent definition. The full consent sentence is quoted verbatim here even though the schema already repeats it in the consent parameter description, which is mild 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?

For a two-call, consent-gated submission tool with no output schema, everything an agent needs is present: the sequencing, what step 1 returns, what step 2 requires, and the downstream email-confirmation behavior.

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%, so the baseline is 3; the description adds value by tying 'answers' to the enquiry_fields sibling, defining what consent actually authorizes, and clarifying that 'confirmation' is the token produced by step 1 and only passed on the second call.

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 verb (submits) and resource (an enquiry to human providers), and immediately rules out two likely misreadings: 'NOT a purchase, NOT a guaranteed quote.' An agent can distinguish it from enquiry_describe and enquiry_fields without opening any schema.

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 two-step protocol is spelled out explicitly: Step 1 with answers+consent=true, then Step 2 only 'if the person agrees' with the confirmation token added. The gating condition for the second call and the prerequisite for step 1 (answers keyed by enquiry_fields) are both stated.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources