ScorpTech x402 Tools

Llms Txt

llms_txt

Read-onlyIdempotent

Read a site's llms.txt (the llmstxt.org convention that tells AI agents where the useful docs are), SSRF-safe: title, summary, details and every section's links (title, absolute URL, notes; "Optional" section flagged), whether llms-full.txt exists, size / token estimate and format issues. Accepts a domain or a direct URL to an llms.txt file. Price: $0.002 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/llms-txt

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": {
      "url": "<url>"
    },
    "name": "llms_txt"
  }
}

Input Schema

Name	Required	Description
`url`	Yes	Domain, site URL or direct URL of an llms.txt / llms-full.txt
`maxLinks`	No
`checkFull`	No	Also check whether /llms-full.txt exists

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, and the description adds real value beyond them: 'SSRF-safe', the exact return fields, the 'Optional' section flag, the llms-full.txt existence check, size/token estimates, format issues, and the x402 pricing/HTTPS endpoint. This is rich behavioral context that the annotations alone would not convey.

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?

Purpose is front-loaded and each clause (return fields, SSRF safety, input flexibility, price/endpoint) carries information. It runs a bit long with the pricing/HTTPS tail, but that tail is useful for an agent deciding whether to pay, so nothing is wasteful.

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?

There is no output schema, and the description fully describes the return shape (title, summary, details, per-section links with title/URL/notes, llms-full.txt existence, size/token estimate, format issues). An agent has enough to call it and interpret the result.

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 67%, with url and checkFull documented. The description's 'whether llms-full.txt exists' reinforces checkFull, but maxLinks has no prose explanation anywhere. This is roughly baseline adequacy with a small gap, so a 3 fits.

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 ('Read') and resource (a site's llms.txt) and even parenthetically defines the convention. It is clearly distinguishable from siblings like web_to_text, robots_sitemap, or url_markdown 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 Guidelines4/5

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

Explains the input flexibility ('Accepts a domain or a direct URL to an llms.txt file'), which tells the agent when it can apply the tool. It does not explicitly contrast with sibling discovery tools, so it stops short of a 5.

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

All ScorpTech x402 Tools 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?