Skip to main content
Glama

Site discovery

site_discovery

Fetch a site's agent-facing files (robots.txt, llms.txt, sitemap, well-known MCP and agent cards, OpenAPI, security.txt) and say what was found. Does not change the site.

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": {
      "domain_or_url": "<domain_or_url>"
    },
    "name": "site_discovery"
  }
}

Input Schema

NameRequiredDescriptionDefault
domain_or_urlYesDomain or http(s) URL, for example example.com.

Output Schema

NameRequiredDescriptionDefault
okNo
filesNo
originNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does add one genuinely useful behavioral fact – 'Does not change the site' (read-only) – and lists which resources are retrieved, but says nothing about what happens when files are absent, whether partial results are returned, redirect/timeouts, rate limits, or auth requirements for protected well-known endpoints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the action and the resource list, closing with the read-only constraint. There is no filler; every clause carries information an agent needs before calling.

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 explanation is rightly omitted, and the tool is low-complexity with a single required parameter. The 'say what was found' clause plus the file enumeration covers the essentials; only failure-mode behavior (missing files, unreachable domain) is left unaddressed.

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 coverage is 100% and the single parameter is fully documented with a format example, so the schema already does the work. The description adds only marginal meaning by implying either a bare domain or a URL is acceptable ('a site's'), which the schema also covers.

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?

The description pairs a specific verb ('Fetch') with a precise resource class ('a site's agent-facing files') and enumerates the exact artifacts (robots.txt, llms.txt, sitemap, well-known MCP and agent cards, OpenAPI, security.txt). That enumeration makes it unmistakable against generic siblings like fetch_page or read_url, which target arbitrary content rather than these well-known discovery paths.

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 implied by the scope: reach for this when you need to discover what agent-facing metadata a domain publishes. However, the description never states when not to use it, nor does it route the agent to fetch_page/read_url/check_url for non-agent-facing content, leaving the boundary with siblings to inference.

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