Skip to main content
Glama

site

by uk.co.businessgrantsfinder

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

submit_enquiry

Submits an enquiry to Business Grants Finder — 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 grant or R&D 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 grant or R&D 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

A5/5.0
Behavior5/5

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

With no annotations, the description fully carries behavioral disclosure. It explains the validation step, the returned summary/consent/token, the two-step submission model, the email with a required click-through link, and that providers only see the enquiry after the link is clicked. Side effects and gating behavior are transparent.

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 longer than average, but every sentence earns its place by documenting a necessary procedural detail. Step 1 and Step 2 are clearly delineated, and the title front-loads the key caveat that this is not a purchase.

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 complex two-step tool with no annotations and no output schema, the description is remarkably complete. It covers what to send, what to expect back, what to show the user, when to proceed, and the post-submission email/click behavior. It even points to enquiry_fields for valid answer keys.

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 schema coverage is 100%, the description adds critical meaning: answers must be keyed by field key from enquiry_fields, consent is only valid when the person has agreed to the exact quoted sentence, and confirmation is the token from step 1 after approval. This goes well beyond the schema's basic property 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 verb and resource ('Submits an enquiry to Business Grants Finder') and explicitly differentiates the tool from a purchase or guaranteed quote. The title reinforces the two-step nature and human-provider target, making the tool's purpose unmistakable.

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 step-by-step usage instructions: when to call once (with answers and consent=true), what to do with the response (show summary and consent line), when to call again (only if the person agrees, adding the confirmation token), and the condition that consent means agreement to the quoted text. It also states when not to use this tool (not for purchase or guaranteed quote).

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 unique role: checker_start initializes the guide, checker_answer advances it, and checker_tree exposes the full decision tree. On the enquiry side, enquiry_describe explains the process, enquiry_fields provides the schema, and submit_enquiry performs the submission. There is no meaningful overlap between tools.

Naming Consistency4/5

Tool names consistently use snake_case and workflow prefixes (checker_ vs enquiry_), which makes grouping easy. However, the grammatical pattern varies: some are noun-led (checker_answer, checker_tree), some verb-led (checker_start, submit_enquiry), and enquiry_describe/enquiry_fields mix the two. This is a minor deviation rather than a chaotic naming scheme.

Tool Count5/5

Six tools is well-scoped for the server's two linked workflows: navigating an eligibility decision guide and submitting a Business Grants Finder enquiry. Each tool earns its place, and there is no redundancy or excessive split.

Completeness5/5

The checker surface provides start, step-by-step navigation, and full tree visibility, while the enquiry surface covers process explanation, field schema, and the two-step consent-based submission. Together they cover the full user journey from eligibility assessment to enquiry submission with no obvious dead ends.

Resources