7702-sweeper-check

How to buy the full sweeper report

full_report_info

Read-onlyIdempotent

Retrieve the endpoint, price, and payment method for the optional paid sweeper report after an unknown EIP-7702 delegation is found; no API call or payment is made.

Instructions

Returns the endpoint, price and payment method of the optional paid sweeper report. It does not call the API and does not pay or sign anything. The paid report analyses each delegate found: bytecode heuristics for sweeper/drainer patterns, source verification, an overall risk level and plain-language advice. It accepts 1-20 addresses per call for 0.01 USDC on Base via x402. Use it after check_7702_delegation reports a delegation that the owner did not set up knowingly. If delegated_on is empty, the paid report adds little. Returns: method, url_template, price_usdc, network, asset, protocol, max_addresses, settles and docs.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`docs`	Yes
`asset`	Yes
`method`	Yes
`network`	Yes
`settles`	Yes
`protocol`	Yes
`price_usdc`	Yes
`url_template`	Yes
`max_addresses`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.1.0Oct 31, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "asset": {
+      "type": "string"
+    },
+    "docs": {
+      "type": "string"
+    },
+    "max_addresses": {
+      "type": "number"
+    },
+    "method": {
+      "type": "string"
+    },
+    "network": {
+      "type": "string"
+    },
+    "price_usdc": {
+      "type": "number"
+    },
+    "protocol": {
+      "type": "string"
+    },
+    "settles": {
+      "type": "string"
+    },
+    "url_template": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "method",
+    "url_template",
+    "price_usdc",
+    "network",
+    "asset",
+    "protocol",
+    "max_addresses",
+    "settles",
+    "docs"
+  ],
+  "type": "object"
+}

First observedv0.1.0Oct 30, 2026

TDQS

A4.8/5.0

Behavior5/5

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

With annotations already covering read-only and non-destructive behavior, the description adds important context: it does not call the API and does not pay or sign anything. It also discloses pricing, network, payment protocol, and address limits for the downstream paid report.

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?

The description is front-loaded and efficient, leading with what the tool returns and immediately clarifying that it does not perform payment or signing. It is somewhat long because it includes report capabilities and a return-field list, but the information is relevant and well organized.

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?

Given the zero-parameter schema, existing output schema, and annotations, the description is complete: it explains purpose, usage conditions, pricing, constraints, and safety behavior. An agent has enough context to choose this tool and understand what it will and will not do.

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?

The tool has zero input parameters, so the schema is complete and the baseline is 4. The description does not introduce confusing required inputs for this tool, though its reference to 1-20 addresses per call pertains to the paid report rather than this info endpoint.

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 states a specific resource and action: it returns the endpoint, price, and payment method for the optional paid sweeper report. It clearly distinguishes itself from the sibling check_7702_delegation tool by explaining that it provides purchasing metadata rather than analyzing delegations.

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?

It gives explicit when-to-use guidance: use it after check_7702_delegation reports a delegation the owner did not knowingly set up. It also gives a when-not-to-use condition: if delegated_on is empty, the paid report adds little.

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

Deploy Server