Skip to main content
Glama
Sign In

site

by uk.co.recruitmentagencyfees
OverviewDiscussionsAdmin

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: "Send my contact details to up to three relevant recruitment agencies, chosen by Recruitment Agency Fees, 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." (with form, that guide's own consent line, which enquiry_fields returns)

Input Schema

NameRequiredDescriptionDefault
formNoa guide's own form, for a different reader (temp-to-perm-transfer-fees); omit for the site's main form
answersYesthe person's answers, keyed by field key
consentYestrue only when the person has agreed to: Send my contact details to up to three relevant recruitment agencies, chosen by Recruitment Agency Fees, 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. (or the chosen form's own consent line)
confirmationNothe confirmation token from step 1, after the person has approved the summary

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields 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 recruitment agencies, chosen by Recruitment Agency Fees, 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 relevant recruitment agencies, chosen by Recruitment Agency Fees, 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. (or the chosen form's own consent line)"
    • addedInput schema / properties / form
      Added value: +{
+  "description": "a guide's own form, for a different reader (temp-to-perm-transfer-fees); omit for the site's main form",
+  "enum": [
+    "temp-to-perm-transfer-fees"
+  ],
+  "type": "string"
+}
  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 recruitment agencies, who'll contact me directly."New value: +"true only when the person has agreed to: Send my contact details to up to three relevant recruitment agencies, chosen by Recruitment Agency Fees, 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 well: it discloses validation, returned summary/consent line/token, email verification before providers see details, and data sharing to up to three agencies with opt-out. This gives strong side-effect and consent context for a submission tool.

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?

The description front-loads purpose and the two-step process, and the step structure makes it easy to follow. It is somewhat long because it repeats full consent wording and adds a parenthetical form note, though most of that length is justified by the legal/consent disclosure.

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?

There is no output schema or annotation coverage, yet the description explains what Step 1 returns, what Step 2 does, and the email-link verification flow before providers can see the enquiry. This is complete enough for an agent to invoke the tool correctly in both steps.

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 100%, so the baseline is 3; the description adds workflow meaning by clarifying that answers are keyed by field key from enquiry_fields and that Step 2 reuses the same answers plus the confirmation token. It does not add much beyond the schema for the form parameter, but it meaningfully clarifies how confirmation is used.

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 and resource: submits an enquiry to Recruitment Agency Fees, explicitly not a purchase or guaranteed quote, and frames the two-step process. An agent can distinguish this from enquiry_fields/enquiry_describe because those fetch form metadata while this submits the enquiry.

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?

Gives explicit step-by-step usage: Step 1 call with answers and consent=true, then show the summary and consent line; Step 2 only after the person agrees, with the same answers and confirmation token. It also points to enquiry_fields as the source of field keys.

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