ikeytz - Schlüsseldienst Ludwigsburg

Get Llms Mcp Web

get_llms_mcp_web

Read-only

WHAT: Fetch /llms-mcp-web.txt — browser WebMCP catalog (early bootstrap tools + full list). Same executeMcpTool handlers as HTTP /mcp, different transport (document.modelContext). USE for WebMCP/UI discovery copy. Prefer get_llms_mcp_server for the machine/server catalog text; prefer get_llms_txt for the general site llms index. Optional offset/limit — see schema. Not this streamable-http endpoint itself.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum number of lines to return after offset. Omit or null = return every remaining line in the loaded file. Clamped to 1..10000. For sitemap.txt (~9076 http-URLs, Stand 2026-09-22) omit limit to get the full list (or page with offset/limit + nextOffset). For llms-keywords.txt prefer a window; the file is huge. Meta also as trailing # MCP-META lines in summary.
`offset`	No	0-based line index into the fetched UTF-8 file (split on \n). 0 = first line. Omit = 0. Combined with limit = a sliding window. Use nextOffset from the previous result to page. Does not count bytes; one line can be a long URL.

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes	true = use summary, canonicalUrl, and extra keys. false = do not invent data; read error + hint and retry with valid args or open hint.
`hint`	No	Present when ok=false. Absolute URL the agent should open or pass to get_ai_page / get_discovery.
`path`	No	Public path on www, e.g. /llms.txt or /.well-known/ai.txt
`tool`	Yes	Echo of the tool name that produced this object (e.g. get_service_area).
`error`	No	Present when ok=false. Codes include: unknown_tool, unknown_place, unknown_auswahl, unknown_ratgeber, unknown_doc, unknown_discovery, faq_not_found, wissen_not_found, serp_not_found, q_required, bad_datetime, bad_when_key, plus HTTP errors from fetch.
`limit`	No	Applied line limit, or null if the caller omitted limit.
`which`	No	Resolved discovery id after alias fold (llms, sitemap-txt, ard, ai-catalog, …).
`locale`	No	Locale actually used for URLs (args.locale or de).
`offset`	No	Applied 0-based line offset.
`related`	No	Always includes https://www.ikeytz.com/llms.txt. Geo tools also include https://maps.ikeytz.com/llms.txt.
`summary`	No	Primary text for the model. For discovery tools this is the file window (possibly thousands of characters). For list tools a compact one-liner. Quote with attribution.
`totalUrls`	No	http(s) lines in the loaded file (full count when public/ read succeeds).
`truncated`	No	true if load hit a byte cap OR offset+limit left more lines. Also mirrored in trailing # MCP-META lines in summary.
`nextOffset`	No	offset + returnedLines when more lines remain in the loaded file; else null. Pass as the next offset. Also in # MCP-META.
`totalBytes`	No	Full origin file size when Content-Length is present (e.g. llms-keywords ~50MB); else character length of the downloaded body before the load cap. Also in # MCP-META.
`totalChars`	No	Character length of the downloaded body before applying discoveryFetchMax (may equal totalBytes for ASCII).
`totalLines`	No	Line count of the loaded file (full public/ file when available).
`attribution`	Yes	Required citation: 'Quelle: Schlüsseldienst Ludwigsburg ikeytz (ikeytz.com) · ai-train=no · https://www.ikeytz.com/.well-known/ai.txt'
`canonicalUrl`	No	Best URL to show the user: https://www.ikeytz.com… page, or tel:+49…, mailto:…, https://wa.me/…. Prefer this over constructing URLs.
`returnedUrls`	No	Lines in this window that start with http(s)://
`bytesReturned`	No	UTF-8 byte length of the returned body window (before # MCP-META).
`returnedLines`	No	How many lines are in summary/body this call (before # MCP-META).
`fetchTruncated`	No	true if discoveryFetchMax cut the load (line-boundary safe). Large discovery files (sitemap-xml ~12MB, llms-keywords ~55MB, llms-index ~2MB) must load full so offset/limit can reach EOF.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 25, 2026

changedOutput schema / properties / fetchTruncated / description

Previous value: -"true if discoveryFetchMax cut the load (line-boundary safe). sitemap-xml (~12MB) and llms-index (~2MB) must load full; keywords stay capped — use totalBytes."New value: +"true if discoveryFetchMax cut the load (line-boundary safe). Large discovery files (sitemap-xml ~12MB, llms-keywords ~55MB, llms-index ~2MB) must load full so offset/limit can reach EOF."

Changed1 schema field changedSep 25, 2026

changedOutput schema / properties / fetchTruncated / description

Previous value: -"true if discoveryFetchMax cut the load (line-boundary safe). sitemap-xml must load full (~12MB cap); keywords stay capped — use totalBytes."New value: +"true if discoveryFetchMax cut the load (line-boundary safe). sitemap-xml (~12MB) and llms-index (~2MB) must load full; keywords stay capped — use totalBytes."

Changed3 schema fields changedSep 24, 2026

changedOutput schema / properties / fetchTruncated / description

Previous value: -"true if a byte cap cut the load (line-boundary safe). Rare for sitemap.txt (reads public/)."New value: +"true if discoveryFetchMax cut the load (line-boundary safe). sitemap-xml must load full (~12MB cap); keywords stay capped — use totalBytes."

addedOutput schema / properties / totalBytes

Added value: +{
+  "description": "Full origin file size when Content-Length is present (e.g. llms-keywords ~50MB); else character length of the downloaded body before the load cap. Also in # MCP-META.",
+  "type": "number"
+}

addedOutput schema / properties / totalChars

Added value: +{
+  "description": "Character length of the downloaded body before applying discoveryFetchMax (may equal totalBytes for ASCII).",
+  "type": "number"
+}

Changed8 schema fields changedSep 22, 2026

changedInput schema / properties / limit / description

Previous value: -"Maximum number of lines to return after offset. Omit or null = return every remaining line in the fetch window (not the whole disk file if the fetch itself truncated). Clamped to 1..10000. For sitemap.txt (~807 URL lines) omit limit to get the full list. For llms-keywords.txt prefer a window; the file is huge."New value: +"Maximum number of lines to return after offset. Omit or null = return every remaining line in the loaded file. Clamped to 1..10000. For sitemap.txt (~9076 http-URLs, Stand 2026-09-22) omit limit to get the full list (or page with offset/limit + nextOffset). For llms-keywords.txt prefer a window; the file is huge. Meta also as trailing # MCP-META lines in summary."

changedOutput schema / properties / bytesReturned / description

Previous value: -"UTF-8 byte length of the returned body window."New value: +"UTF-8 byte length of the returned body window (before # MCP-META)."

addedOutput schema / properties / fetchTruncated

Added value: +{
+  "description": "true if a byte cap cut the load (line-boundary safe). Rare for sitemap.txt (reads public/).",
+  "type": "boolean"
+}

changedOutput schema / properties / nextOffset / description

Previous value: -"offset + returnedLines when more lines remain; else null. Pass as the next offset."New value: +"offset + returnedLines when more lines remain in the loaded file; else null. Pass as the next offset. Also in # MCP-META."

changedOutput schema / properties / returnedLines / description

Previous value: -"How many lines are in summary/body this call."New value: +"How many lines are in summary/body this call (before # MCP-META)."

changedOutput schema / properties / totalLines / description

Previous value: -"Line count of the fetched text (after byte cap)."New value: +"Line count of the loaded file (full public/ file when available)."

changedOutput schema / properties / totalUrls / description

Previous value: -"http(s) lines in the fetched text."New value: +"http(s) lines in the loaded file (full count when public/ read succeeds)."

changedOutput schema / properties / truncated / description

Previous value: -"true if fetch hit a byte cap OR offset+limit left more lines."New value: +"true if load hit a byte cap OR offset+limit left more lines. Also mirrored in trailing # MCP-META lines in summary."

Changed1 schema field changedSep 2, 2026

changedOutput schema / properties / which / description

Previous value: -"Resolved discovery id after alias fold (llms, sitemap-txt, ai-catalog, …)."New value: +"Resolved discovery id after alias fold (llms, sitemap-txt, ard, ai-catalog, …)."

First observedSep 1, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description adds real context beyond that: the file serves the same executeMcpTool handlers as HTTP /mcp over a different transport (document.modelContext), and it's a bootstrap catalog. It stops short of describing rate limits or content shape, but with an output schema present that is a minor gap.

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?

Front-loaded with WHAT/USE/Prefer labels and zero filler sentences; every clause carries routing or scoping information. The telegraphic style and parenthetical asides are dense but still readable, costing it a point on structure rather than size.

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?

For a read-only fetch tool with full parameter documentation, an output schema, and safety annotations, the description covers purpose, transport semantics, sibling routing, and an explicit exclusion. Nothing an agent needs to invoke it correctly is missing.

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 schema itself explains line-based offset/limit, clamping, and nextOffset paging in detail. The description only says 'Optional offset/limit — see schema', which defers rather than adds meaning, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Fetch) and resource (/llms-mcp-web.txt) with its scope: 'browser WebMCP catalog (early bootstrap tools + full list)'. It explicitly distinguishes itself from get_llms_mcp_server and get_llms_txt, so an agent can route without opening any schema.

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

Usage Guidelines5/5

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

Explicit 'USE for WebMCP/UI discovery copy' plus two named alternatives with the condition that selects each ('Prefer get_llms_mcp_server for the machine/server catalog text; prefer get_llms_txt for the general site llms index'). It even adds an exclusion ('Not this streamable-http endpoint itself').

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All ikeytz - Schlüsseldienst Ludwigsburg tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?