Skip to main content
Glama

book_free_check

The free Fifty Asks check: we ask ChatGPT, Perplexity and Gemini the questions a customer would ask for your trade and town, fifty times in all, and record who each one names first. You get a short written report by email: who gets named, whether you do, and the page facts the named businesses share. Free, no card, no contract. We do not promise rankings or how often an assistant names you. Booked by an agent: delivered within 2 business days instead of 5.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "business": "<business>",
      "trade": "<trade>",
      "city": "<city>",
      "contact_name": "<contact_name>",
      "email": "<email>"
    },
    "name": "book_free_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesTown and state served, e.g. Round Rock, TX
emailYesWhere the report or calendar invite goes
notesNoAnything we should know
tradeYese.g. plumber, HVAC, roofer, electrician
websiteNoBusiness website, if any
businessYesBusiness name
agent_nameNoWhich agent you are (e.g. product and version)
contact_nameYesThe person the booking is for (your human)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/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 fairly well: it discloses cost (free, no card, no contract), the delivery channel (email), an SLA (within 2 business days for agent bookings vs 5 otherwise), and an explicit limitation ('we do not promise rankings or how often an assistant names you'). It stops short of stating whether the booking is confirmed immediately, how to cancel, or what happens if the email is invalid.

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 front-loaded with what the tool does before moving to terms and SLA, and each sentence carries information (mechanism, deliverable, price, caveat, turnaround). It is somewhat long and pitch-flavored — 'Free, no card, no contract' restates itself — but nothing is genuinely wasted.

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?

For an eight-parameter booking tool with full schema coverage and no output schema, the description covers what is submitted (trade, town, contact, email), what comes back (emailed report on who gets named), cost, and turnaround. The main gap is post-booking behavior — confirmation, scheduling or cancellation — which an agent may need before committing a user.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the eight parameters and their examples are already documented in the schema and the baseline applies. The description adds only loose context by mentioning the trade, the town, and the email destination, without clarifying fields like agent_name or notes beyond what the schema states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific deliverable (the 'Fifty Asks check'), the exact mechanism (ask ChatGPT, Perplexity and Gemini customer-style questions for a trade and town fifty times, record who is named first), and the output (a written report by email). An agent can tell this is a booking for a free AI-visibility audit rather than a call or visit request, though it never explicitly contrasts itself with siblings like book_call or request_visit.

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

Usage Guidelines3/5

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

Usage is implied: book this when a business wants a free AI-visibility report for a trade and town. There is no explicit when-to-use or when-not statement and no named alternative, so an agent choosing between this, book_call and request_visit must infer the distinction from the description's content alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources