Agent Tools

url_dossier

One call dossier on a web page and its host: clean markdown, page metadata, outbound links and extracted fields, plus domain intelligence (registrar, age, DNS, SPF, DMARC) and IP network lookup for the host, with a short trust summary. Replaces three calls. Price $0.007 USDC per call via x402. Example output: {"url":"https://example.com/","host":"example.com","page":{"title":"Example Domain","word_count":25},"domain":{"registered":true,"registrar":"RESERVED-Internet Assigned Numbers Authority"},"ip":{"network":"EDGECAST","country":"US"},"summary":{"domain_age_days":11000,"has_spf":true,"https_reachable":

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

Input Schema

Name	Required	Description	Default
`url`	Yes	Public page URL

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 26, 2026

TDQS

A3.6/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does a decent job: it discloses the composite nature of the call, the exact price ($0.007 USDC via x402), and shows an example response emboldening the shape. It does not cover auth flow beyond pricing, rate limits, or failure behavior, which is a gap for a paid multi-source aggregation call.

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

Conciseness3/5

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

The purpose is front-loaded, which is good, but the trailing example JSON is truncated mid-string ('https_reachable":') and bloats the definition without completing the illustration. The price sentence could be shorter. Overall readable but not tight.

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?

No output schema exists, and the example output covers the key returned sections (page, domain, ip, summary), which is the right compensation. For a composite paid tool, error handling and partial-failure semantics (e.g., what if DNS fails) are unaddressed, keeping it below a 5.

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?

Only one parameter, and the schema already describes it as 'Public page URL' at 100% coverage. The description implies the URL is a public page (matching 'Public page URL') but adds no format rules, scheme constraints, or redirect handling. Baseline 3 is appropriate since the schema does the work.

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?

The description states a concrete resource (a web page and its host) and enumerates exactly what the dossier contains: markdown, metadata, outbound links, extracted fields, domain intelligence, IP network lookup, and a trust summary. The verb is light ('one call dossier'), but the content list is specific enough that an agent immediately knows the payload. It does not name the sibling tools it supersedes, only 'replaces three calls'.

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?

'Replaces three calls' implies when this should be preferred over smaller siblings, but the three are never named (plausibly url_metadata, domain_lookup, ip_lookup). There are no exclusions or prerequisites beyond the payment note. The agent must infer when to use this versus the granular siblings.

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

All Agent 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?