Skip to main content
Glama

check_sanctions__receipt

Verifiable screening receipt: runs the screen and returns the exact records checked with a hash. 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/receipt

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__receipt"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/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 disclose important behavior: it runs the screen, returns the exact checked records plus a hash, costs $0.01 per call, and requires x402 payment in params._meta. However, it does not clarify idempotency, whether charges apply on failure, or what happens if payment is missing.

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?

The description is front-loaded with the tool's purpose, followed by pricing and endpoint details in compact form. It is appropriately sized, though the raw HTTP endpoint is somewhat operational rather than semantic.

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?

For a low-complexity, one-parameter tool, the description covers purpose, payment mechanics, and the hashed return value. It remains incomplete because the sole parameter is unexplained and payment-failure or idempotency behavior is not addressed.

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

Parameters1/5

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

The schema has one optional parameter, 'name', with 0% description coverage, and the description never mentions it. No meaning, filtering behavior, or expected format is added beyond the bare schema field.

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 states a specific verb and resource: it runs a screening and returns the exact records checked with a hash. The 'receipt' framing and hash output clearly distinguish this from a plain screening result, though it does not explicitly name the sibling screen tool it complements.

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 description implies usage through 'verifiable screening receipt' and explains the payment requirement, but it does not explicitly say when to call this instead of the sibling screening or receipt tools. No exclusions or alternative-routing guidance are provided.

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