Skip to main content
Glama

site

by com.conveyancingfeesireland

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

submit_enquiry

Submits an enquiry to Conveyancing Fees Ireland — 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 Irish conveyancing solicitors, who'll quote 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 Irish conveyancing solicitors, who'll quote 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.6/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 it delivers: the two-step call behavior, the confirmation token handoff, the email-activation requirement before any provider sees the enquiry, and the exact consent wording are all disclosed. An agent knows precisely what preconditions and side effects each call has.

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 longer than average but earns its length: every clause carries procedural or exclusionary information, and the Step 1/Step 2 structure makes it scannable. Minor redundancy with the title ('two steps; not a purchase') keeps it from a 5.

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 stateful two-step tool with no output schema and no annotations, the description is complete: it explains the step-1 return values (summary, consent line, token), the condition for step 2, and the email link the person must click. Nothing an agent needs to drive both calls correctly is missing.

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 meaning on top by tying the answers object to 'field key from enquiry_fields' and explaining that the confirmation property is the step-1 token. Consent semantics are reinforced with the exact user-facing wording.

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 action — submitting an enquiry to Conveyancing Fees Ireland — and immediately disambiguates it from a purchase or guaranteed quote. It also names the two-step interaction model, which distinguishes this submission tool from the sibling tools enquiry_describe and enquiry_fields.

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 two-step protocol is explicit: step 1 validates and returns a token, and step 2 is only for after the person agrees, using the same answers plus the token. It gives clear when-not context ('NOT a purchase') but does not explicitly route the agent to sibling tools like enquiry_fields for obtaining the 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
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/5.0
Disambiguation5/5

Each tool has a clearly distinct role: one explains the process, one defines the input schema, and one submits the enquiry. There is no overlap between describing, field discovery, and submission.

Naming Consistency4/5

All tool names use snake_case and mostly follow a noun/verb pattern with 'enquiry' as the common subject. submit_enquiry fits the pattern well, while enquiry_describe and enquiry_fields are noun-led rather than verb-led, but the shared prefix keeps the set predictable.

Tool Count5/5

Three tools is exactly right for this narrow purpose: an explainer, a schema reader, and a submitter. Each tool earns its place and there is no unnecessary surface area.

Completeness5/5

The tool set fully covers the enquiry workflow: an agent can understand the process, fetch all required fields, and submit with proper two-step confirmation. No obvious operations are missing for the stated domain.

Resources