Skip to main content
Glama

site

by uk.co.recruitmentagencyfees

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

submit_enquiry

Submits an enquiry to Recruitment Agency Fees — 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 relevant recruitment agencies, 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 relevant recruitment agencies, 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.9/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 burden of behavioral disclosure, and it does so thoroughly. It reveals the two-step commit pattern, the consent requirement with the exact consent text, the email click-through before any provider sees the enquiry, and the fact that submitting is not a purchase or guarantee.

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, and the two-step structure makes it easy to follow. It front-loads the most critical caveat ('NOT a purchase, NOT a guaranteed quote') and then logically walks through the sequential flow without redundant 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?

This is a complex two-step, consent-gated, email-confirmed submission flow, and the description covers all essential behavior an agent needs to invoke it correctly: validation step, confirmation token, consent semantics, and final submission. There is no output schema or annotations, so the description's completeness is especially valuable.

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?

The schema already covers 100% of parameters, so the baseline is 3. The description adds meaningful context beyond the schema: answers must be keyed by field key from enquiry_fields, consent must reflect the exact stated agreement, and confirmation is the token from step 1 used only after the person approves.

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 a specific verb and resource: submitting an enquiry to Recruitment Agency Fees. It explicitly distinguishes itself from a purchase or guaranteed quote, and the two-step procedure is front and center, so an agent can tell this apart from the sibling enquiry_describe and enquiry_fields tools.

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 invocation guidance: first call without confirmation to validate and get a token, then call again only after the person agrees, including the same answers, consent=true, and the token. It also references enquiry_fields as the source of answer keys, providing a clear prerequisite.

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

Each tool has a clearly distinct purpose: one explains the process, one provides the field schema, and one handles submission. There is no overlap or ambiguity between them.

Naming Consistency3/5

Naming is mixed: two tools use the 'enquiry_' prefix (enquiry_describe, enquiry_fields) while submit_enquiry uses the suffix, and the patterns are noun_verb, noun_noun, and verb_noun. The shared 'enquiry' root keeps it readable, but the convention is not consistent.

Tool Count5/5

Three tools is well-scoped for this narrow domain of submitting an enquiry. Each tool covers a necessary step, and none feel redundant or extraneous.

Completeness5/5

The workflow is fully covered: learn about the process, retrieve the required fields, and submit with consent and confirmation. There are no obvious missing operations for the stated purpose of handling Recruitment Agency Fees enquiries.

Resources