Skip to main content
Glama

check_sanctions__bundle

Counterparty due-diligence bundle in ONE call: sanctions by name and/or wallet, plus domain facts. 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/check-sanctions/bundle

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

Input Schema

NameRequiredDescriptionDefault
nameNo
domainNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A3.6/5.0
Behavior4/5

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

With zero annotations, the description carries the full burden and does well: it discloses the $0.01 USDC cost on Base (eip155:8453), the x402 payment requirement via params._meta["x402/payment"], and the HTTP endpoint. It does not describe the response shape or whether payment is charged on failed lookups.

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 dense sentences, front-loaded with the value proposition, then price/payment, then transport. Almost every clause earns its place; the only waste is the 'and/or wallet' reference that does not correspond to a parameter.

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?

Payment, pricing, and endpoint are fully covered, which is the hardest part for an agent to discover. But with no output schema and no annotations, an agent still cannot tell what the bundled result contains or how sanctions matches and domain facts are structured in 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 coverage is 0%, so the description must compensate. It maps name to sanctions screening and domain to domain facts, but introduces a 'wallet' input that does not exist in the schema and never says both parameters are optional or what an empty call returns.

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: sanctions screening by name/wallet plus domain facts, delivered as a single bundled call. The phrase 'bundle in ONE call' implicitly distinguishes it from the many single-purpose check_sanctions__* siblings, though it never names one; minor drift in saying 'wallet' when the schema exposes only name and domain.

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 'bundle in ONE call' framing implies when to prefer this over the individual screenings, and 'name and/or wallet' implies either input alone suffices. But there is no explicit when-not guidance, no statement that both parameters are optional and what happens if neither is supplied, and no named alternative.

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