Skip to main content
Glama

Caelara Labs SEO & GEO Readiness

llms_txt_auditor

Fetch and audit /llms.txt (and llms-full.txt) against the llms.txt format

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": {
      "url": "<url>"
    },
    "name": "llms_txt_auditor"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesAny URL on the target site

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose a genuine behavior beyond the name — that it fetches both /llms.txt and llms-full.txt and validates against the format — but says nothing about network/read-only nature, what happens when the file is missing or malformed, or whether the audit is strict or advisory.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence with no filler, and the verb-plus-resource core is front-loaded. Nothing could be cut without losing content.

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?

For a one-parameter fetch-and-validate tool the description covers the what, but with no output schema it should also hint at the shape of results (pass/fail findings, which rules are checked). Failure behavior for a missing or unreachable llms.txt is likewise unaddressed.

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% and the single parameter is already documented as 'Any URL on the target site'. The description's mention of both llms.txt and llms-full.txt subtly confirms the agent need not supply a file path, but adds no syntax, normalization, or domain-scoping detail beyond the schema.

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 pairs a specific verb ('Fetch and audit') with a specific resource ('/llms.txt (and llms-full.txt)') and names the standard it validates against. That is enough to distinguish it from all listed siblings (robots checks, link scanners, hreflang, schema.org), none of which touch llms.txt, though the description itself does not say so.

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 only implied: an agent can infer this is the tool for llms.txt compliance work. There is no explicit 'use when' statement, no prerequisites (e.g., site must be publicly reachable), and no mention of how it relates to ai_bot_robots_check or geo_readiness_composite.

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