Skip to main content
Glama

APEX Agent Safety & Guardrails

Threat intel bulk

threat_intel_bulk
Read-onlyIdempotent

Full X1 machine-readable scam blacklist and related-wallet cluster graph. $0.025 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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

Input Schema

NameRequiredDescriptionDefault
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, openWorld), and the description adds what annotations cannot: the price ($0.025/call), accepted payment rails, and the two-phase terms-then-pay handshake. It does not describe the response shape or payload size, which for a paid data purchase is a remaining gap.

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?

Three tight sentences, front-loaded with the payload description before the pricing and the call sequence. No filler; each sentence carries distinct information (what, cost/rails, how to call).

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?

With one optional parameter and no output schema, the description carries the burden of describing the return value, and it does so at a high level (machine-readable blacklist plus cluster graph). It is nearly complete; more detail on payload format or volume would close the last gap.

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 100%, so baseline is 3, but the description earns more by explaining the workflow semantics of `payment`: what happens without it (terms returned) and what happens with it (purchase completes inline). That is meaning beyond the schema's static field description.

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?

States a specific resource and scope: a full X1 scam blacklist plus a related-wallet cluster graph. An agent knows exactly what data it is buying. It does not, however, distinguish itself from the sibling threat_intel or bulk_screener, so the 'bulk' differentiator is left implicit.

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?

Gives a clear procedural path for invocation (call without payment, sign terms, call again with payment), which is genuine when-to-use guidance. It says nothing about when to choose this over the sibling threat_intel or exit_check tools, so alternative selection is left to inference.

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.