Skip to main content
Glama

Grid402 — Brazil Public Data & Network Oracle

grid402_ofac

Read-onlyIdempotent

Global Sanctions (OFAC SDN / UN) and Base Mainnet EVM wallet AML inspection (0.0200 USDC / 4 credits).

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": {
      "target": "<target>"
    },
    "name": "grid402_ofac"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetYesEVM address (0x...) or entity name to screen against OFAC/UN lists.
payment_tx_hashNoOptional txHash on Base Mainnet, Session Pass token (pass_g402_...), EIP-3009 base64 payload, or demo for Sandbox.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world behavior, so the safety profile is covered. The description adds genuinely useful non-schema context in the form of pricing (0.0200 USDC / 4 credits), which affects invocation decisions. However, it says nothing about billing failure modes, what happens with an unpaid or invalid payment payload, or whether the call errors versus degrades.

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?

A single front-loaded sentence with the resource scope first and the cost in a trailing parenthetical. Nothing is wasted, though the dense parenthetical mixes pricing into what is otherwise a scope statement.

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 only two parameters and full schema coverage, the structural load is light and annotations cover the safety profile. But there is no output schema, and the description never characterizes what a screening result contains (risk score, match list, verdict), which leaves a real gap for an agent that must interpret the response.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so both parameters (target, payment_tx_hash) are already documented in the schema, including accepted payment forms like pass_g402_ tokens and EIP-3009 payloads. The description adds no parameter-level meaning of its own, so the baseline 3 applies.

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?

The description names concrete resources and actions: screening a target against OFAC SDN / UN sanctions lists plus AML inspection of a Base Mainnet EVM wallet. That is specific enough to distinguish it from generic siblings like grid402_crypto or grid402_compliance. It stops short of differentiating itself from the near-identical sibling grid402_sanctions, so it is not 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, no prerequisites, and no pointer to alternatives such as grid402_sanctions or grid402_kyb_audit. Usage must be inferred entirely from the tool name and schema.

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.