Skip to main content
Glama

get_x402_traffic_diligence

Read-only

Use when you need attested know-your-agent diligence on inbound x402 traffic to Stratalize. Reports settlement count, tool-call concentration, cadence, traffic classification, and sweep-bot heuristics for wallets that have paid Stratalize — plus optional CDP Bazaar listing metadata for a target resource URL. $0.50 USDC per call.

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": {
      "wallet_address": "<wallet_address>"
    },
    "name": "get_x402_traffic_diligence"
  }
}

Input Schema

NameRequiredDescriptionDefault
resource_urlNo
wallet_addressYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description earns credit for adding two things annotations cannot: the $0.50 USDC per-call cost and the fact that results only exist for wallets that have already paid Stratalize. It stops short of describing latency, pagination, or failure modes for unpaid wallets.

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?

Two sentences, front-loaded with the usage trigger, then the payload contents, the optional add-on, and the price. Dense but every clause carries information; only the repeated "Stratalize" branding is slightly redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the enumeration of reported fields is the right substitute and covers the essentials. Still missing for a paid, open-world query: what an empty result means (no paid traffic vs. unknown wallet), address format expectations, and any latency or volume caveats.

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?

Schema description coverage is 0%, so the description must carry parameter meaning and it largely does: wallet_address is implicitly the inbound payer wallet being assessed, and resource_url is tied to optional CDP Bazaar listing metadata. Neither required-ness nor address format is restated, but the conceptual role of both parameters is clear.

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?

Names a specific subject (attested know-your-agent diligence on inbound x402 traffic to Stratalize) and enumerates the concrete metrics returned: settlement count, tool-call concentration, cadence, traffic classification, sweep-bot heuristics. It implicitly separates itself from the seller-side sibling by focusing on inbound payer wallets, though it never names an alternative explicitly.

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?

"Use when you need attested know-your-agent diligence" gives a triggering condition, and the phrase "wallets that have paid Stratalize" scopes eligibility. However, there is no when-not guidance, no mention of when to reach for get_x402_seller_statement or the general diligence siblings instead, and no prerequisite/authentication notes.

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