Skip to main content
Glama
chia-mcp

chia-mcp

Official
by Chia-Network

get_coin_records_by_hint

Read-only

Find coin records tagged with a hint, optionally filtered by spent status and creation height range. Verify asset IDs because hints are attacker-controlled and may return fake airdrop coins.

Instructions

Find coin records by hint. Hints are typically used in CAT and NFT transactions to tag coins with additional metadata (like the inner puzzle hash). WARNING: Hints are attacker-controlled — anyone can create a coin hinting any puzzle hash for a few mojos. Results may include unsolicited/fake-airdrop coins. Always verify asset IDs. Optionally filter by spent status and height range.

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": {
      "hint": "<hint>"
    },
    "name": "get_coin_records_by_hint"
  }
}

Input Schema

NameRequiredDescriptionDefault
hintYesThe hint to search for (0x-prefixed hex string)
end_heightNoOnly return coins created before this height
start_heightNoOnly return coins created at or after this height
include_spent_coinsNoInclude coins that have been spent (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A3.9/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true, so the description carries the interesting behavioral burden and does so well: it discloses that hints are attacker-controlled, that anyone can spend a few mojos to hint any puzzle hash, that results may contain unsolicited or fake-airdrop coins, and that the caller must verify asset IDs. This is exactly the kind of adversarial-input context an agent cannot get from structured fields.

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 purpose is front-loaded, followed by the definition, the security warning, and the optional filters in a sensible order. The final sentence partly duplicates the schema's include_spent_coins and height parameters, and could be trimmed without loss.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description still covers the critical risk of untrusted results and the available filters, which is the main thing an agent needs. It omits result shape, ordering, and any limits on how many records are returned, and does not mention the batch sibling — minor gaps for a read-only lookup.

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 baseline is 3. The description adds conceptual meaning to the hint parameter (inner puzzle hash tagging) beyond the schema's "0x-prefixed hex string", but the spent-status and height-range sentence merely restates parameters the schema already documents with defaults and bounds.

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?

"Find coin records by hint" gives a specific verb and resource and the following sentences clarify what a hint is. It does not, however, distinguish itself from the closely named sibling get_coin_records_by_hints (singular vs. plural batch lookup), leaving that disambiguation to inference.

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?

It provides real context about when hints exist (CAT and NFT transactions tagging coins with metadata such as the inner puzzle hash), which helps an agent decide whether a hint lookup is the right approach. It never states when to prefer a sibling such as get_coin_records_by_puzzle_hash or the plural hints variant, and offers no explicit exclusions.

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