Skip to main content
Glama

walletprofile__sanctions

Exact-address OFAC SDN screen for a Base address. This is an exact-match screen only, not a full compliance check and not legal advice. Price: $0.01 per call in USDC on Base (eip155:8453), paid with x402 in params._meta["x402/payment"]. HTTP: GET https://api.firstmention.uk/s/walletprofile/sanctions

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": {
      "address": "<address>"
    },
    "name": "walletprofile__sanctions"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesBase address, 0x + 40 hex.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / address / description
      Added value: +"Base address, 0x + 40 hex."
    • addedInput schema / required
      Added value: +[
      +  "address"
      +]
  2. Changed1 schema field changed
    • removedInput schema / properties / range_blocks
      Removed value: -{
      -  "type": "number"
      -}
  3. Changed3 schema fields changed
    • removedInput schema / properties / address / description
      Removed value: -"0x-prefixed 20-byte Base address"
    • removedInput schema / properties / range_blocks / description
      Removed value: -"How many recent blocks to scan (2000-20000, default 20000)"
    • removedInput schema / required
      Removed value: -[
      -  "address"
      -]
  4. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the price ($0.01 per call), the currency and chain (USDC on eip155:8453), the x402 payment location in params._meta, and the HTTP method and endpoint. It stops short of describing the response shape or any failure/rate-limit behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with what the tool is, followed by limitations, then payment mechanics and endpoint. Every sentence carries information the caller needs; nothing is padded.

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?

For a single-parameter read tool with no annotations and no output schema, the description covers purpose, scope limits, cost, payment protocol, and transport. The main remaining gap is that the response format (match/no-match, list details) is not hinted at.

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% and the schema already documents the single address parameter's format. The description adds real value beyond the schema by explaining the out-of-band payment parameter (params._meta['x402/payment']) that is not represented in the input schema at all.

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 verb and resource: an OFAC SDN exact-address screen for a Base address, plus the exact endpoint. An agent knows precisely what it does. It does not, however, differentiate itself from similar siblings such as check_sanctions__address or x402check__screen, so it stops short of a 5.

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?

The 'exact-match screen only, not a full compliance check and not legal advice' clause communicates the limits of the tool, which is genuine usage context. But it names no alternative tool for a deeper compliance check or for similar screening, so the agent is left to infer which sibling to use instead.

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