Skip to main content
Glama

Get llms.txt map

get_llms_map
Read-onlyIdempotent

Return the site’s llms.txt map (short) or llms-full.txt (full). Education only, not financial advice.

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": "get_llms_map"
  }
}

Input Schema

NameRequiredDescriptionDefault
variantNoshort returns llms.txt (site map); full returns llms-full.txt (all content). Default: short.short

Output Schema

NameRequiredDescriptionDefault
urlYes
textYes
variantYes
disclaimerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "disclaimer": {
      +      "type": "string"
      +    },
      +    "text": {
      +      "type": "string"
      +    },
      +    "url": {
      +      "type": "string"
      +    },
      +    "variant": {
      +      "enum": [
      +        "short",
      +        "full"
      +      ],
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "variant",
      +    "url",
      +    "disclaimer",
      +    "text"
      +  ],
      +  "type": "object"
      +}
  2. Changed2 schema fields changed
    • addedInput schema / properties / variant / default
      Added value: +"short"
    • addedInput schema / properties / variant / description
      Added value: +"short returns llms.txt (site map); full returns llms-full.txt (all content). Default: short."
  3. First observed

TDQS

A3.6/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 fully covered. The description adds only that the full variant returns all content and a content disclaimer ("Education only, not financial advice"), with no detail on size, rate limits, or truncation behavior.

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?

Two short sentences, front-loaded with the action and variant mapping. The trailing disclaimer is brief and relevant to the returned content, though it borders on boilerplate.

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?

With one fully documented optional parameter, rich annotations, and an output schema, nothing material is missing. The description names both variants and the resource, which is sufficient for correct invocation.

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 100% and the single enum parameter already documents "short returns llms.txt; full returns llms-full.txt". The description restates rather than extends that meaning, so the baseline 3 applies.

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?

"Return the site's llms.txt map (short) or llms-full.txt (full)" gives a specific verb and resource and immediately names the two content variants, so an agent knows exactly what it fetches. It does not explicitly distinguish itself from siblings like get_guide or list_directory, keeping it short of a 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?

Usage is only implied: an agent can infer this is the tool for retrieving the site's llms.txt index rather than individual posts. There is no statement of when to prefer it over search_content or list_directory, and no exclusions or prerequisites.

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