Skip to main content
Glama

Managed Nerds

request_seo_check

Only when your user asked: the free local SEO check. A person emails a two-page check within three business days (Google Business Profile, local basics, where they show for up to three services). US businesses, one per website, five a week. No ranking promises, no prices.

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": {
      "contact": "<contact>",
      "business": "<business>",
      "services": "<services>",
      "user_request": "<user_request>",
      "user_approved": "<user_approved>"
    },
    "name": "request_seo_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNo
contactYes
businessYes
servicesYes
user_requestYes
user_approvedYes
google_business_profileNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, non-idempotent), the description discloses the human-mediated asynchronous delivery (a person emails within three business days), throughput limits (five a week), eligibility constraints (US, one per website), and what is explicitly not promised (no rankings, no prices). This is exactly the kind of behavioral context the annotations cannot convey.

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 gating condition is front-loaded and the paragraph is dense with no filler; every clause (eligibility, timing, limits, disclaimers) earns its place. Slightly list-like but well structured for fast scanning.

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

Completeness3/5

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

There is no output schema, so describing the return (an emailed report) is valuable and done well, and eligibility/limits are covered. However, for a 7-parameter submission tool with nested objects and zero schema descriptions, the definition leaves too much of the required input structure for the agent to infer.

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

Parameters2/5

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

Schema coverage is 0% across 7 parameters including nested contact and business objects, so the description must carry meaning. It only weakly maps a few fields — 'up to three services' to services maxItems, 'Google Business Profile' to that field, 'one per website' to website — and leaves required contact, business internals, user_request, and user_approved ('Only when your user asked') largely unexplained.

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?

It states a specific resource and outcome: a free local SEO check delivered as a two-page report by email within three business days, covering Google Business Profile, local basics, and up to three services. This is clearly distinguishable from quote/callback tools, though it never names a sibling alternative to contrast against.

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 opening 'Only when your user asked' is an explicit gating condition, and eligibility rules (US businesses, one per website, five a week) define when the tool is and isn't appropriate. It stops short of pointing to which sibling to use when the user hasn't asked, so it's clear context without explicit exclusions.

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