Skip to main content
Glama

site

by com.tradesseoagency

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

submit_enquiry

Submits an enquiry to Trades SEO Agency — 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 marketing 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 marketing 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.6/5.0
Behavior5/5

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

With no annotations, the description carries full burden and does so thoroughly: step 1 only validates and returns a summary/token, step 2 actually submits and sends an email, and providers only see the enquiry after the person clicks the link. It also spells out the exact consent text.

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 densely packed with necessary procedural steps and caveats. It is front-loaded with the core purpose and exclusions, then structured into Step 1 and Step 2. The length is justified by the two-step workflow, though it could be tightened slightly.

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?

It covers step-1 return values (summary, consent line, confirmation token), step-2 outcome (submission, email, link click), and consent semantics. Missing details like step-2 return value or error cases are minor given the complexity already explained.

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 vital meanings: answers must be keyed by field key from enquiry_fields, consent is only valid with the specified agreement text, and confirmation is the step-1 token used in step 2. This goes well beyond the schema's bare property names.

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 Trades SEO Agency', then immediately disambiguates with 'NOT a purchase, NOT a guaranteed quote'. This clearly differentiates the tool from any purchase-related sibling and states the two-step nature.

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?

It gives explicit step-by-step instructions: Step 1 with answers and consent=true, Step 2 with confirmation token only if the person agrees. It also states what consent must mean. It does not explicitly contrast with sibling tools like compare_options, but the procedural context is clear enough.

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

A3.6/5.0
Disambiguation5/5

The six tools split cleanly into two clear groups: three comparison-read tools (criteria, options, table) and three enquiry-flow tools (describe, fields, submit). Each tool has a distinct responsibility, and the descriptions make it obvious which one to call for a given need.

Naming Consistency4/5

The naming is mostly consistent and predictable, using clear prefixes like compare_ and enquiry_. The main deviation is that submit_enquiry is verb-first while compare_criteria, compare_options, and compare_table are noun-first, which is a minor but noticeable inconsistency.

Tool Count5/5

Six tools is a well-scoped size for a server that covers a comparison view plus an enquiry submission flow. Each tool earns its place, and there is no redundancy or bloat.

Completeness5/5

The comparison surface is complete: agents can see criteria, options, and the full value table. The enquiry surface is also complete with an orientation tool, a schema tool, and a two-step submission tool, so there are no obvious dead ends.

Resources