Prax Data Services

Search Prax intel

search

Read-onlyIdempotent

Search Prax threat intelligence in plain words (e.g. 'critical attacker wallets on base this week', 'phishing contracts created by 0x...'). Returns COUNTS of matching addresses (by band, chain, role) plus approved alerts from the last 24 h; address lists are not enumerable - look a specific address up with screen_wallet. Filters: chain (eth, base...), risk band (critical, high), role (attacker wallet, malicious contract, deployer, funding ancestry, clone), period (today, last 7 days, since 2026-10-01), free text (bytecode clone, phishing), 'created by 0x...', 'counterparties of 0x...'. An exact address or tx hash returns that record's id. Use fetch(id) for the full record. Business plan and above.

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": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`query`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, and the description still adds meaningful behavior: results are COUNTS grouped by band/chain/role plus approved alerts from the last 24h, lists are not enumerable, and an exact address or tx hash resolves to a record id. The only gap is that it doesn't touch result volume or how the 24h alert window interacts with the period filter.

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?

Dense but front-loaded: purpose first, then return shape, then constraints, then how to reach related tools. Every clause carries information, though the long parenthetical filter list sits mid-paragraph and slightly delays the usage routing.

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?

With no output schema, the description still explains what comes back (counts by band/chain/role, 24h alerts, record ids on exact match) and where to go for full detail. For a two-parameter search tool this covers everything an agent needs to call it correctly.

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 coverage is 0%, so the description must carry parameter meaning, and it does so extensively for `query` — enumerating supported filters (chain, risk band, role, period, free text, 'created by', 'counterparties of') with example values. The `limit` parameter is never mentioned, leaving cap/truncation behavior to the schema's default 25 and maximum 50.

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?

Opens with a specific verb and resource ('Search Prax threat intelligence') and specifies the input modality ('in plain words') with two concrete example queries. It also distinguishes itself from siblings by stating that address lists are not enumerable and pointing to screen_wallet and fetch.

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?

Explicitly routes the agent: specific address lookups go to screen_wallet, and full records go to fetch(id). It also names the plan prerequisite ('Business plan and above'), which is a real usage gate rather than a vague hint.

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

All Prax Data Services 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.