Hedera Toolbox

identity_check_sanctions

Screen Hedera accounts against on-chain risk signals including transaction patterns, counterparty risk, and known flagged accounts to identify potential sanctions violations.

Instructions

Screen a Hedera account against on-chain risk signals including transaction patterns, counterparty risk, and known flagged accounts. Costs 0.5 HBAR.

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": {
      "api_key": "<api_key>",
      "account_id": "<account_id>"
    },
    "name": "identity_check_sanctions"
  }
}

Input Schema

Name	Required	Description	Default
`api_key`	Yes	Your HederaIntel API key
`account_id`	Yes	Hedera account ID to screen

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.4.5Mar 18, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations provided, the description carries full burden. It discloses the cost (0.5 HBAR) and the screening purpose, but doesn't mention authentication requirements (though api_key parameter implies it), rate limits, response format, or what constitutes 'risk signals' beyond the listed categories. The description adds some behavioral context but leaves significant gaps for a tool with no annotations.

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 a single, efficient sentence that states the core purpose and includes important cost information. It's appropriately sized and front-loaded with the main functionality. The cost information at the end is valuable context that earns its place.

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 tool with no annotations and no output schema, the description provides basic purpose and cost information but lacks details about what the screening actually returns, how risk is assessed, or error conditions. Given the complexity of risk screening and absence of structured behavioral information, the description should do more to explain what users can expect from this operation.

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 the schema already documents both parameters fully. The description doesn't add any parameter-specific information beyond what's in the schema. The baseline score of 3 is appropriate when the schema does all the parameter documentation work.

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 clearly states the tool's purpose: 'Screen a Hedera account against on-chain risk signals' with specific risk categories listed (transaction patterns, counterparty risk, flagged accounts). It distinguishes from siblings like identity_verify_kyc by focusing on sanctions/risk screening rather than KYC verification. However, it doesn't explicitly contrast with all similar tools like identity_resolve.

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 context through 'screen a Hedera account against on-chain risk signals' and mentions the cost (0.5 HBAR), which suggests when this tool might be appropriate. However, it lacks explicit guidance on when to use this vs. alternatives like identity_verify_kyc or identity_resolve, and doesn't specify prerequisites or exclusions.

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