Skip to main content
Glama

Draft an llms.txt for a site

draft_llms
Read-onlyIdempotent

Draft an llms.txt from the domain's own homepage and up to 25 declared pages, using their titles and descriptions. A draft for the owner to cut down, not a publication.

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": {
      "domain": "<domain>"
    },
    "name": "draft_llms"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds real substance beyond that: the page cap (25), the fact that content comes from titles/descriptions rather than page bodies, and that output is explicitly a draft rather than publishable. It doesn't say what happens when a site has few or no declared pages.

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?

Two sentences, front-loaded with the action and sources, then the caveat. Every clause carries information; nothing is padding.

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?

With no output schema, the description does enough by naming the artifact and its sources, and only leaves minor gaps: the exact return format and error behavior for unreachable or empty sites.

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 0% for the single 'domain' parameter, so the description must carry the load. It implies the value is a site domain whose homepage gets fetched, but it doesn't specify accepted format (bare domain vs URL vs subdomain) or what happens with invalid input, leaving a meaningful gap.

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 verb and artifact ('Draft an llms.txt') and specifies the input sources: the domain's homepage and up to 25 declared pages, using their titles and descriptions. No sibling tool produces llms.txt, but the description doesn't explicitly contrast with anything, so it stops short of 5.

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?

The phrase 'A draft for the owner to cut down, not a publication' implies an intended workflow (human review, non-authoritative output), which is useful context. However, it never states prerequisites (e.g., must the domain be resolved or scanned first?), nor when to prefer a different tool such as scan_domain or resolve_domain.

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.