Skip to main content
Glama
Sign In

automaton

by uk.firstmention.api
OverviewDiscussionsAdmin

check_sanctions__seller

Buyer preflight: sanctions screen plus domain RDAP facts plus a live x402 probe of the endpoint you are about to pay. 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/seller

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

Input Schema

NameRequiredDescriptionDefault
nameNo
domainNo
endpointNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • removedInput schema / properties / address
      Removed value: -{
-  "description": "Crypto wallet address to screen",
-  "type": "string"
-}
    • removedInput schema / properties / domain / description
      Removed value: -"Domain to look up RDAP registration facts"
    • addedInput schema / properties / endpoint
      Added value: +{
+  "type": "string"
+}
    • removedInput schema / properties / name / description
      Removed value: -"Company or entity name to screen"
    • removedInput schema / properties / threshold
      Removed value: -{
-  "description": "Match similarity threshold, default 0.85",
-  "maximum": 1,
-  "minimum": 0.5,
-  "type": "number"
-}
  2. Changed6 schema fields changed
    • addedInput schema / properties / address
      Added value: +{
+  "description": "Crypto wallet address to screen",
+  "type": "string"
+}
    • addedInput schema / properties / domain
      Added value: +{
+  "description": "Domain to look up RDAP registration facts",
+  "type": "string"
+}
    • addedInput schema / properties / name / description
      Added value: +"Company or entity name to screen"
    • addedInput schema / properties / threshold
      Added value: +{
+  "description": "Match similarity threshold, default 0.85",
+  "maximum": 1,
+  "minimum": 0.5,
+  "type": "number"
+}
    • removedInput schema / properties / url
      Removed value: -{
-  "type": "string"
-}
    • removedInput schema / properties / wallet
      Removed value: -{
-  "type": "string"
-}
  3. Changed7 schema fields changed
    • removedInput schema / properties / address
      Removed value: -{
-  "description": "Seller payee wallet address; wallet is an alias.",
-  "type": "string"
-}
    • removedInput schema / properties / domain
      Removed value: -{
-  "description": "Seller domain for RDAP facts.",
-  "type": "string"
-}
    • removedInput schema / properties / endpoint
      Removed value: -{
-  "description": "Live x402 endpoint URL to probe for its 402 terms.",
-  "type": "string"
-}
    • removedInput schema / properties / name / description
      Removed value: -"Seller or company name; company is an alias."
    • removedInput schema / properties / threshold
      Removed value: -{
-  "description": "Minimum fuzzy score, default 0.85.",
-  "type": "number"
-}
    • addedInput schema / properties / url
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / wallet
      Added value: +{
+  "type": "string"
+}
  4. Changed5 schema fields changed
    • addedInput schema / properties / address
      Added value: +{
+  "description": "Seller payee wallet address; wallet is an alias.",
+  "type": "string"
+}
    • addedInput schema / properties / domain / description
      Added value: +"Seller domain for RDAP facts."
    • addedInput schema / properties / endpoint / description
      Added value: +"Live x402 endpoint URL to probe for its 402 terms."
    • addedInput schema / properties / name / description
      Added value: +"Seller or company name; company is an alias."
    • addedInput schema / properties / threshold
      Added value: +{
+  "description": "Minimum fuzzy score, default 0.85.",
+  "type": "number"
+}
  5. Added

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations, the description carries the load and does disclose the two hardest facts: cost ($0.01 per call in USDC on Base, eip155:8453) and the payment mechanism (x402 payload in params._meta["x402/payment"]). That is genuine behavioral context an agent cannot infer from the schema. It stops short of describing what the three probes return or how partial failures behave.

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 operation and followed by the commercial and transport facts; nothing is padding. The HTTP URL line is arguably redundant with the tool binding, but it earns a small place as a debugging aid.

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 paid, three-source composite with no output schema and no annotations, the description covers payment and endpoint but leaves the call contract underspecified: no return shape, no note on which parameters are needed, and no failure or refund semantics for a tool that charges per call.

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

Parameters2/5

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

Schema description coverage is 0% and all three parameters (name, domain, endpoint) are bare strings with no required set. The description only obliquely touches "endpoint" via "the endpoint you are about to pay"; it says nothing about what name or domain are used for, whether they are alternatives, or what happens when they are omitted.

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?

"Buyer preflight: sanctions screen plus domain RDAP facts plus a live x402 probe" names a concrete composite operation over three named data sources, and "the endpoint you are about to pay" scopes the target. It is not a tautology of the tool name, and the composite nature distinguishes it from a single-domain screen, though it never names a sibling explicitly.

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 phrase "Buyer preflight" and "the endpoint you are about to pay" imply the trigger condition: run this before paying an x402 seller. That is a real contextual cue, but there is no explicit when-not, no mention of the many adjacent seller-check tools (txpreflight__seller, x402_preflight__check, pageaudit__sellercheck, domain_intel__seller), and no guidance on choosing among them.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All automaton toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources