Skip to main content
Glama

Read LLM discovery file

read_llm_discovery
Read-onlyIdempotent

Fetch IntoDNS.ai agent discovery files such as llms.txt, llms-full.txt, or OpenAPI specs to get canonical citation URLs, prompt-ready context, and machine-readable API routing details.

Instructions

Read-only fetch of an IntoDNS.ai LLM/agent discovery file: llms.txt (canonical agent index), llms-full.txt (full prompt-ready context), llms.json (structured prompt routing), llm/api.md (Markdown API guide), openapi.json (OpenAPI 3.1 spec) or postman.json (Postman collection). Defaults to llms.txt. Use when an agent needs canonical citation URLs, machine-readable API surface, or prompt-routing hints for IntoDNS.ai itself; use get_citation_guidance for a topic-narrowed citation list. Pure HTTPS GET, no auth, no side effects.

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

Input Schema

NameRequiredDescriptionDefault
fileNoDiscovery file to fetch; defaults to llms.txtllms.txt

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.11.1
    • addedInput schema / properties / file / description
      Added value: +"Discovery file to fetch; defaults to llms.txt"
  2. Changed1 schema field changedv1.10.0
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered; the description still adds the auth and transport facts ('pure HTTPS GET, no auth') that annotations cannot express. It stops short of warning that llms-full.txt/llms.json may be large or verbose, which is the one behavioral risk for an agent pulling full context into a prompt.

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 sentences, front-loaded with the verb and resource, then the file enumeration, then the usage routing. The long parenthetical list in sentence one is dense but every gloss earns its place because the filenames are otherwise uninformative.

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 one optional parameter, rich annotations and no output schema, the definition covers everything needed to invoke it correctly. The remaining gap is payload-scale guidance for the full-context variants, a minor omission given the tool's simplicity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single enum already carries the default, so the baseline is 3. The description goes beyond it by glossing four of the six opaque filename values ('llms-full.txt (full prompt-ready context)', 'llms.json (structured prompt routing)'), which the enum names alone do not convey.

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 and resource ('Read-only fetch of an IntoDNS.ai LLM/agent discovery file') and enumerates exactly which artifacts it returns. It explicitly draws the boundary against the sibling get_citation_guidance, so an agent can separate the two without opening either 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?

Gives concrete selection criteria ('when an agent needs canonical citation URLs, machine-readable API surface, or prompt-routing hints') and names the alternative for a different need ('use get_citation_guidance for a topic-narrowed citation list'). Both when-to-use and when-to-use-something-else are present.

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