automaton

company_facts__lookup_wallet

Full OFAC digital-currency address record for one wallet address. 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/company-facts/lookup/wallet

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

Input Schema

Name	Required	Description	Default
`address`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 6, 2026
- addedInput schema / properties / address
```
Added value: +{
+  "type": "string"
+}
```
- removedInput schema / properties / company
```
Removed value: -{
-  "type": "string"
-}
```

Changed3 schema fields changedNov 6, 2026

removedInput schema / properties / address

Removed value: -{
-  "description": "EVM (0x...) wallet address to screen",
-  "type": "string"
-}

addedInput schema / properties / company
```
Added value: +{
+  "type": "string"
+}
```
removedInput schema / required
```
Removed value: -[
-  "address"
-]
```

AddedNov 6, 2026

TDQS

B3.4/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 behavioral burden and does usefully disclose the $0.01 USDC-on-Base price, x402 payment location in params._meta, and the HTTP GET endpoint. However, it does not describe error behavior, rate limits, response shape, or whether the address is required, leaving clear gaps.

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 compact and front-loads the purpose before giving price, payment, and endpoint details. It is mostly tight, though the raw HTTP endpoint is somewhat implementation-level rather than task-level guidance.

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 simple one-parameter lookup with no output schema, the description identifies the returned record and important payment mechanics. It is only adequate, however, because it omits address format/required semantics and comparison guidance against closely related sibling tools.

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?

The schema has a single 'address' string parameter with 0% description coverage. The description adds domain meaning by indicating it is a wallet address for an OFAC digital-currency record, but it does not specify address format, supported chains, or required status.

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 operation and resource: a full OFAC digital-currency address record for one wallet address. An agent can understand the core purpose without opening the schema, though it does not explicitly distinguish itself from related siblings such as company_facts__lookup, lookup_batch, or check_sanctions__address.

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 'for one wallet address' implies single-address usage and implicitly contrasts with batch lookup, but there is no explicit guidance on when to use this versus company_facts__lookup, lookup_batch, or sanctions-specific alternatives. The usage context is inferable but not fully stated.

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

All automaton tools Inspect

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

Need Help?