Skip to main content
Glama

ikeytz Einsatzgebiet-Karten

Get Llms Txt

get_llms_txt
Read-only

WHAT: Alias get_discovery(which=llms) — maps /llms.txt 1:1 with optional offset/limit. USE as the primary maps machine index. NEXT: get_ai_txt, get_sitemap_txt, get_links.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of lines to return after offset. Omit or null = if remaining payload ≤~30KB return all remaining lines; if larger, return first ~30KB window + nextOffset (O9). Explicit limit keeps 1..10000 line window (MCP caps unchanged — not forced to 30KB). Meta also as trailing # MCP-META lines in summary.
offsetNo0-based index into a list or discovery file lines (split on \n). 0 = first. Omit = 0. Combine with limit to page. Use nextOffset / offset+limit from a previous result when present.

Output Schema

NameRequiredDescriptionDefault
okYestrue = use summary, canonicalUrl, and extra keys. false = do not invent data; read error + hint and retry with valid args or open hint.
hintNoPresent when ok=false. Absolute URL or short recovery hint the agent should open or pass to another tool.
pathNoPublic relative path of the file on maps
textNoUTF-8 line window (file body before # MCP-META). Same bytes as summary without meta trailer.
toolYesEcho of the tool name that produced this object (e.g. get_service_area).
errorNoPresent when ok=false. Codes include: unknown_place, unknown_discovery, unknown_doc, q_required, plz_required, coords_required, outside_service_area, url_required, not_maps_host, bad_url, path_or_url_required, serp_not_found, slug_or_coords_required, path_required.
limitNoApplied line limit, or null if omitted
whichNoResolved discovery id (ard, ai-catalog, llms, robots, sitemap-txt, llms-mcp-server, …).
localeNoLocale actually used for URLs. maps is German-only: always de (MAPS-E8 — no /en on maps). Requested non-de is ignored; payload locale=de.
offsetNoApplied 0-based line offset
missingNotrue if the discovery file was not found on disk
relatedNoAlways includes https://maps.ikeytz.com/llms.txt.
summaryNoPrimary text for the model. For discovery tools this is the file window. For list tools a compact one-liner. Quote with attribution.
totalUrlsNohttp(s) lines in the full file
truncatedNotrue if offset+limit left more lines. Also in trailing # MCP-META.
nextOffsetNoPass as next offset when truncated; else null. Also in # MCP-META.
totalBytesNoFull discovery file size in bytes (UTF-8). Also in trailing # MCP-META.
totalCharsNoFull discovery file character length before offset/limit. Also in # MCP-META.
totalLinesNoAlias of total_lines
attributionYesRequired citation: 'Quelle: Schlüsseldienst Ludwigsburg ikeytz (ikeytz.com) · ai-train=no · https://maps.ikeytz.com/.well-known/ai.txt'
total_linesNoLine count of the full file
canonicalUrlNoBest URL to show the user: https://maps.ikeytz.com… page, public embed JSON, tel:+49…, mailto:…, https://wa.me/…, or a www pointer. Prefer this over constructing URLs.
returnedUrlsNohttp(s) lines in this window
bytesReturnedNoUTF-8 length of text window
returnedLinesNoLines in this window (before # MCP-META)
fetchTruncatedNotrue if a load cap cut the file before paging (www Cap). maps reads full from disk → always false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum items or lines to return after offset. Omit = all remaining in the window (subject to tool-specific clamps). For geo near-search default is often 5 without radius_km, up to 52 with radius."New value: +"Maximum number of lines to return after offset. Omit or null = if remaining payload ≤~30KB return all remaining lines; if larger, return first ~30KB window + nextOffset (O9). Explicit limit keeps 1..10000 line window (MCP caps unchanged — not forced to 30KB). Meta also as trailing # MCP-META lines in summary."
    • addedInput schema / properties / limit / maximum
      Added value: +10000
  2. Changed3 schema fields changed
    • addedOutput schema / properties / fetchTruncated
      Added value: +{
      +  "description": "true if a load cap cut the file before paging (www Cap). maps reads full from disk → always false.",
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / totalBytes
      Added value: +{
      +  "description": "Full discovery file size in bytes (UTF-8). Also in trailing # MCP-META.",
      +  "type": "number"
      +}
    • addedOutput schema / properties / totalChars
      Added value: +{
      +  "description": "Full discovery file character length before offset/limit. Also in # MCP-META.",
      +  "type": "number"
      +}
  3. Changed9 schema fields changed
    • removedOutput schema / properties / body
      Removed value: -{
      -  "description": "UTF-8 text window after offset/limit",
      -  "type": "string"
      -}
    • addedOutput schema / properties / bytesReturned
      Added value: +{
      +  "description": "UTF-8 length of text window",
      +  "type": "number"
      +}
    • addedOutput schema / properties / nextOffset
      Added value: +{
      +  "description": "Pass as next offset when truncated; else null. Also in # MCP-META.",
      +  "type": [
      +    "number",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / returnedLines
      Added value: +{
      +  "description": "Lines in this window (before # MCP-META)",
      +  "type": "number"
      +}
    • addedOutput schema / properties / returnedUrls
      Added value: +{
      +  "description": "http(s) lines in this window",
      +  "type": "number"
      +}
    • changedOutput schema / properties / text / description
      Previous value: -"Alias/window of body when present"New value: +"UTF-8 line window (file body before # MCP-META). Same bytes as summary without meta trailer."
    • addedOutput schema / properties / totalLines
      Added value: +{
      +  "description": "Alias of total_lines",
      +  "type": "number"
      +}
    • addedOutput schema / properties / totalUrls
      Added value: +{
      +  "description": "http(s) lines in the full file",
      +  "type": "number"
      +}
    • addedOutput schema / properties / truncated
      Added value: +{
      +  "description": "true if offset+limit left more lines. Also in trailing # MCP-META.",
      +  "type": "boolean"
      +}
  4. Changed6 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Maximum items or lines to return after offset. Omit = all remaining in the window (subject to tool-specific clamps). For geo near-search default is often 5 without radius_km, up to 52 with radius."
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • addedInput schema / properties / offset / default
      Added value: +0
    • addedInput schema / properties / offset / description
      Added value: +"0-based index into a list or discovery file lines (split on \\n). 0 = first. Omit = 0. Combine with limit to page. Use nextOffset / offset+limit from a previous result when present."
    • addedInput schema / properties / offset / minimum
      Added value: +0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "description": "Always the same envelope. tools/call returns content[0].text = summary (or JSON) AND structuredContent = this object. On success ok=true with summary + canonicalUrl + extra fields. On failure ok=false with error (snake_case code) and hint (recovery URL). Never writes, never submits forms, never books. Attribution must be kept when quoting. Policy: ai-input yes with attribution; ai-train=no. Host is maps.ikeytz.com (geo/Einsatzgebiet). Prices/FAQ/legal HTML live on www — maps only points.",
      +  "properties": {
      +    "attribution": {
      +      "description": "Required citation: 'Quelle: Schlüsseldienst Ludwigsburg ikeytz (ikeytz.com) · ai-train=no · https://maps.ikeytz.com/.well-known/ai.txt'",
      +      "type": "string"
      +    },
      +    "body": {
      +      "description": "UTF-8 text window after offset/limit",
      +      "type": "string"
      +    },
      +    "canonicalUrl": {
      +      "description": "Best URL to show the user: https://maps.ikeytz.com… page, public embed JSON, tel:+49…, mailto:…, https://wa.me/…, or a www pointer. Prefer this over constructing URLs.",
      +      "type": "string"
      +    },
      +    "error": {
      +      "description": "Present when ok=false. Codes include: unknown_place, unknown_discovery, unknown_doc, q_required, plz_required, coords_required, outside_service_area, url_required, not_maps_host, bad_url, path_or_url_required, serp_not_found, slug_or_coords_required, path_required.",
      +      "type": "string"
      +    },
      +    "hint": {
      +      "description": "Present when ok=false. Absolute URL or short recovery hint the agent should open or pass to another tool.",
      +      "type": "string"
      +    },
      +    "limit": {
      +      "description": "Applied line limit, or null if omitted",
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "locale": {
      +      "description": "Locale actually used for URLs. maps is German-only: always de (MAPS-E8 — no /en on maps). Requested non-de is ignored; payload locale=de.",
      +      "enum": [
      +        "de"
      +      ],
      +      "type": "string"
      +    },
      +    "missing": {
      +      "description": "true if the discovery file was not found on disk",
      +      "type": "boolean"
      +    },
      +    "offset": {
      +      "description": "Applied 0-based line offset",
      +      "type": "number"
      +    },
      +    "ok": {
      +      "description": "true = use summary, canonicalUrl, and extra keys. false = do not invent data; read error + hint and retry with valid args or open hint.",
      +      "type": "boolean"
      +    },
      +    "path": {
      +      "description": "Public relative path of the file on maps",
      +      "type": "string"
      +    },
      +    "related": {
      +      "description": "Always includes https://maps.ikeytz.com/llms.txt.",
      +      "items": {
      +        "format": "uri",
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "summary": {
      +      "description": "Primary text for the model. For discovery tools this is the file window. For list tools a compact one-liner. Quote with attribution.",
      +      "type": "string"
      +    },
      +    "text": {
      +      "description": "Alias/window of body when present",
      +      "type": "string"
      +    },
      +    "tool": {
      +      "description": "Echo of the tool name that produced this object (e.g. get_service_area).",
      +      "type": "string"
      +    },
      +    "total_lines": {
      +      "description": "Line count of the full file",
      +      "type": "number"
      +    },
      +    "which": {
      +      "description": "Resolved discovery id (ard, ai-catalog, llms, robots, sitemap-txt, llms-mcp-server, …).",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "ok",
      +    "tool",
      +    "attribution"
      +  ],
      +  "type": "object"
      +}
  5. First observed

TDQS

A3.6/5.0
Behavior3/5

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

readOnlyHint=true already communicates the safety profile of this read. The description adds that the output is a 1:1 map of /llms.txt (no transformation), which is useful fidelity context, but says nothing about size limits, paging behavior, or rate limits beyond what the schema's offset/limit descriptions already cover.

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?

Very compact and front-loaded: the identity/alias is stated first, then usage, then related calls. The 'NEXT:' list is the weakest element — it is short but its intent (follow-up vs alternative) is unclear, so it earns slightly less than a perfect score.

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?

An output schema exists, so return-value detail is not required, and the annotations cover the safety profile. What remains — purpose, alias relationship, and basic routing — is covered, though the ordering/next-step semantics are left slightly underspecified for a tool that sits in a family of related discovery endpoints.

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%, so the offset/limit semantics — including the ~30KB auto-window and nextOffset behavior — are fully documented in the schema. The description only restates 'optional offset/limit', adding no meaning beyond it; 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?

Names the concrete resource (/llms.txt) and its verb (get/map 1:1), and clarifies the relationship to a sibling by stating it is an alias for get_discovery(which=llms). It also positions itself against nearby tools (get_ai_txt, get_sitemap_txt, get_links) as the 'primary maps machine index'. The phrasing is telegraphic, but an agent can tell what is returned and how it differs from the other *_txt tools.

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

Usage Guidelines4/5

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

'USE as the primary maps machine index' gives explicit selection guidance, which is more than most definitions provide. However, 'NEXT: get_ai_txt, get_sitemap_txt, get_links' is ambiguous — it does not say whether those are alternatives to prefer in some cases or follow-up calls, and no when-not-to-use condition is given.

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