Four x402 tools: endpoint checks, extraction, evidence verification, domain intelligence.
Scored across 5 tools
griddata_domain is clearly distinct, but gridextract_markdown and moneygrid_fetch both fetch a URL and return text with evidence metadata, while gridverify_evidence and gridwatch_preflight both probe a URL and return risk flags/SHA-256. The descriptions clarify intended use cases, but the overlapping boundaries still risk misselection.
All names use snake_case, but the prefix and action pattern is inconsistent: four tools use 'grid...' and one uses 'moneygrid...', while actions mix verbs (fetch, verify, watch, extract) and nouns (data_domain). The lack of a predictable verb_noun convention makes the set feel ad hoc.
5 tools is well-scoped for a read-only evidence/retrieval service, covering DNS resolution, web fetching, markdown extraction, evidence verification, and endpoint preflight. The count is neither thin nor excessive.
For a read-only evidence and content retrieval server, the surface covers the core capabilities: DNS resolution, web fetching, markdown extraction, evidence verification, and endpoint preflight. Minor gaps exist (e.g., no batch operations or structured domain reputation), but core workflows are covered.
Paid read-only domain intelligence. Resolves current public DNS A-record data and returns timestamped hashed evidence. Use when an agent needs current domain/DNS evidence without maintaining its own resolver.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Public http/https URL whose hostname should be inspected. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover read-only, open-world, idempotent, and non-destructive behavior. The description adds valuable context beyond those: the tool is paid, returns timestamped hashed evidence, and resolves current public DNS A-record data. No contradiction with annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two tight sentences front-load the core identity ('Paid read-only domain intelligence'), then explain behavior, output, and the intended use case. Every sentence earns its place with no redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a single-parameter, read-only tool with rich annotations and no output schema, the description is complete: it covers what it does, the nature of the output, the paid aspect, and when to use it. Nothing essential is missing for an agent to decide on and invoke the call.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, and the schema already documents the single 'url' parameter as a public http/https URL whose hostname is inspected. The description does not add additional parameter-level meaning beyond what the schema provides, so a baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb-resource pairing ('resolves current public DNS A-record data') and names the output ('timestamped hashed evidence'). The 'Paid read-only domain intelligence' framing clearly distinguishes it from sibling tools like gridextract_markdown, gridverify_evidence, and gridwatch_preflight.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly says when to use the tool: 'when an agent needs current domain/DNS evidence without maintaining its own resolver.' It gives clear context but does not explicitly name alternatives or exclusion conditions, so it stops short of the full 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Paid read-only web extraction for agents. Fetches one public web URL and returns bounded clean text plus evidence hash and receipt metadata. Use when an agent needs compact machine-readable page content.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Public http/https page URL including scheme. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover read-only, idempotent, and non-destructive behavior-tweak. The description adds valuable context beyond that: the operation is paid, returns bounded output, and includes an evidence hash and receipt metadata. It repeats 'read-only' from the annotation, but the additional behavioral signals are meaningful. It omits failure modes or rate limits, though the core behavior is transparent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three short sentences with no filler: a compact label, a behavior statement, and a usage condition. It is front-loaded with the purpose and avoids redundancy. Every sentence earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple one-parameter tool with read-only/idempotent annotations and no output schema, the description captures the essential behavior, output components, and usage context. It doesn't specify exact boundaries or pricing details, but an agent has enough information to invoke the tool correctly. Minor omissions prevent a perfect score.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% for the single url parameter, including format and description. The description's 'one public web URL' reinforces the schema but doesn't add new semantic meaning. With full schema coverage, a baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: 'Fetches one public web URL and returns bounded clean text plus evidence hash and receipt metadata.' This precisely identifies the tool's action and output. It implicitly distinguishes from sibling tools like griddata_domain and gridverify_evidence, which target different resources and operations.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives an explicit usage condition: 'Use when an agent needs compact machine-readable page content.' This tells the agent when the tool is appropriate. It doesn't explicitly name alternatives or state when not to use it, but the provided context is clear enough for routing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Paid read-only URL evidence preflight ($0.05). Checks HTTP accessibility and operational risk flags, with response-sample hash and timestamp. Does not fact-check claims, establish source credibility, or verify factual truth.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Public http/https evidence URL including scheme. |
$0.02 read-only endpoint preflight. Use before an agent depends on or pays an unfamiliar API, webhook or URL. Returns reachability, HTTP status, latency, risk flags and SHA-256 evidence. Rejects private/local hosts and malformed URLs; unreachable/upstream failures are returned explicitly rather than fabricated.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Public http/https endpoint URL including scheme. Private/local hosts and nonstandard ports are rejected. |
DEFAULT ($0.01/call). Fetch fresh content from one public HTTP/HTTPS URL and return up to 100k characters of machine-ready text with source metadata, timestamp and SHA-256 provenance. Use for web retrieval when you need current source content. Rejects private/local hosts, unsupported schemes, invalid URLs, oversized inputs, and upstream timeouts; failed upstream requests return explicit status/error information.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Public HTTP/HTTPS URL including scheme. Private/local hosts and nonstandard ports are rejected. |
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
moneygrid_fetchgriddata_domain2 fields changedInput schema / properties / url / descriptionAdded value: +"Public http/https URL whose hostname should be inspected."Input schema / properties / url / formatAdded value: +"uri"gridextract_markdown2 fields changedInput schema / properties / url / descriptionAdded value: +"Public http/https page URL including scheme."Input schema / properties / url / formatAdded value: +"uri"gridverify_evidence2 fields changedInput schema / properties / url / descriptionAdded value: +"Public http/https evidence URL including scheme."Input schema / properties / url / formatAdded value: +"uri"gridwatch_preflight2 fields changedInput schema / properties / url / descriptionAdded value: +"Public http/https endpoint URL including scheme. Private/local hosts and nonstandard ports are rejected."Input schema / properties / url / formatAdded value: +"uri"griddata_domaingridextract_markdowngridverify_evidencegridwatch_preflight1 field changedInput schema / additionalPropertiesRemoved value: -falsegridwatch_preflightx402-paid tools: EU company & sanctions data, web search, LLM chat, crypto intel, x402 monitoring.
Free tools: x402 endpoint directory + probe, on-chain x402 demand signal, sudoku, API pricing.
MCP tools for agents: web research, content extraction, email, DNS, and blockchain intelligence.
9 utility tools for agents: DNS, WHOIS, email, IP, URL, headers, QR, text, tech. x402 on Base.
Add one secure layer between your agents and this server.