Skip to main content
Glama

site

by uk.co.employmentcontractgenerator

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

submit_enquiry

Submits an enquiry to Employment Contract Generator — 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 employment solicitors and HR consultancies, 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 employment solicitors and HR consultancies, 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.5/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 and succeeds. It discloses the stateful two-step process, validation behavior, the returned summary/consent/token, the requirement to reuse the token, and the email-link prerequisite before providers see the enquiry. It even includes 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long, but the length is justified by the two-step stateful process. It is front-loaded with the core purpose and the 'not a purchase' warning, then follows a clear Step 1/Step 2 structure. The consent text is somewhat redundant with the schema, but it is a critical legal/consent detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and no annotations, the description covers the essential workflow, state transitions, user consent handling, and the email-link condition well. It does not describe validation error behavior or what happens if consent=false, but for a two-step submission tool the provided context is largely sufficient.

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, but the description adds meaningful workflow semantics beyond the schema: answers are keyed by field keys from enquiry_fields, consent must be true only after the person agrees to the stated text, and the confirmation token is created in step 1 and reused in step 2.

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 opens with a specific verb and resource: 'Submits an enquiry to Employment Contract Generator' and immediately disambiguates with 'NOT a purchase, NOT a guaranteed quote.' The title adds 'to human providers (two steps; not a purchase),' and the two-step workflow clearly distinguishes this from sibling enquiry/checker tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit step-by-step instructions: Step 1 call with answers and consent=true, show the summary and consent line; Step 2 call again only if the person agrees, including the confirmation token. It also references the sibling tool enquiry_fields for answer keying, providing useful routing context, though it does not enumerate exclusions for every sibling.

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

The tools split cleanly into two workflows: the interactive checker (start, answer, tree) and the enquiry form (describe, fields, submit). Within each group, every tool has a distinct role, and the tree tool is clearly framed as the full end-to-end view rather than a step-by-step interaction.

Naming Consistency4/5

Most tools follow a clear domain prefix pattern: checker_* and enquiry_*, with lowercase snake_case names. submit_enquiry breaks the prefix convention slightly, but it is still a plain verb_noun name and easily understood, so the overall pattern remains predictable.

Tool Count5/5

Six tools is well-scoped for a site with two core features: a decision guide and a contact/enquiry flow. Each tool covers a necessary step without redundancy or bloat.

Completeness5/5

The checker workflow is complete with start, step-by-step navigation, and the full tree for end-to-end reasoning. The enquiry workflow is also complete with an overview, field schema, and a two-step consent-aware submission process, leaving no obvious dead ends.

Resources