Skip to main content
Glama

Site fixes

site_fixes

Audit the live site the way AI crawlers and Google read it (robots rules for AI crawlers, firewall, rendering, indexing, canonicals, page titles and descriptions, structured data, sitemap, llms.txt, internal links to key pages, share images, answer pages) and return fix specs { id, theme, page, issue, evidence, fix } grouped by theme, one PR per theme, minus fixes already shipped. Costs $0.02 from the balance, charged only when it returns. Nothing is charged when it finds nothing to fix. When you record the PR, put the fix ids in meta.fixIds so they are not suggested again. The robots fix is the whole corrected robots.txt, with a note on each crawler it changes for the PR. Training crawlers (GPTBot, ClaudeBot, CCBot...) are the founder's call: while they have not answered, that fix carries fix.choices, the whole file for allow, block and keep; ask, use the one they pick, and put their answer in the PR's record as meta.training so later checks follow it.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "site_fixes"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoA page on this workspace's site. Default: the homepage
trainingNoThe founder's answer on training crawlers: allow (let them in), block (keep them out), keep (leave robots.txt as it is for them). Kept for later checks; left out, the last answer stands

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / training
      Added value: +{
      +  "description": "The founder's answer on training crawlers: allow (let them in), block (keep them out), keep (leave robots.txt as it is for them). Kept for later checks; left out, the last answer stands",
      +  "enum": [
      +    "allow",
      +    "block",
      +    "keep"
      +  ],
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

The tool provides rich behavioral transparency far beyond the standard inputs/outputs. It explicitly details the cost structure ($0.02 on return, free if nothing found), workflow requirements (writing the entire corrected robots.txt), and specific instructions for handling training crawlers.

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 exceptionally detailed, covering too many facets for a truly concise summary. However, given the complexity of the tool and the need to convey workflow rules (cost, PR metadata, crawler logic), this level of length is highly justified and logically structured.

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?

The tool is highly complex and lacks an output schema. The description is remarkably complete, covering the audit criteria, the fix specification structure, the PR workflow, the financial model, and specific internal field requirements, making it entirely self-contained.

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?

Since the schema coverage is 100%, the baseline is high. The description adds value by detailing the semantic implications of the 'training' enum, defining what 'allow,' 'block,' and 'keep' mean in the context of robots.txt and subsequent checks.

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 tool is clearly defined as an audit function that reviews a live site against specific technical and SEO standards, including AI crawlers, structured data, and robots rules. It distinguishes itself from general crawl tools by focusing on generating 'fix specs' and 'PRs' based on these detailed criteria.

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

Usage Guidelines5/5

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

The description provides extensive guidance on usage, detailing not only what is audited but also the resulting output structure—fixes are grouped by theme, resulting in one PR per theme. It also specifies unique operational constraints, such as managing `meta.fixIds` to prevent repetitive suggestions.

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