Skip to main content
Glama

llms.txt index builder

bpj_llms_txt_builder
Read-onlyIdempotent

Build a curated text index for AI readers using a site title, summary and reference links.

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": {
      "title": "<title>",
      "summary": "<summary>",
      "resources": "<resources>"
    },
    "name": "bpj_llms_txt_builder"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes
summaryYes
resourcesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds only that the produced artifact is a curated text index aimed at AI readers; it says nothing about where the output goes, whether it is returned as a string or written to a path, or how it handles invalid URLs.

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?

A single front-loaded sentence with no filler; the artifact and the three inputs appear immediately. It is efficiently sized for a three-parameter builder, though a second sentence oriented toward usage or output would have earned its place.

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

Completeness2/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 the description carries the burden of explaining what is returned, and it does not. Combined with the undocumented resource-line syntax and no guidance on link validity or duplicate handling, an agent could invoke this correctly on inputs but would not know what to expect back.

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 description coverage is 0%, and the description maps one-to-one to the three required fields (site title, summary, reference links), which is better than nothing. But it does not explain the per-line 'Resource title | absolute URL | summary' format or the length ceilings, which is exactly the kind of meaning the schema titles leave implicit.

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: 'Build a curated text index for AI readers', which makes the llms.txt output recognizable. It does not, however, distinguish this tool from near-neighbors such as bpj_sitemap_xml_builder or the other indexing helpers, so an agent must infer the boundary itself.

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

Usage Guidelines2/5

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

The phrase 'for AI readers' hints at the intended context but gives no explicit when-to-use, when-not-to-use, or alternative. There is no mention of prerequisites (e.g., that a site title and summary must be authored first) or of what to do when the index already exists.

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.