Skip to main content
Glama
chia-mcp

chia-mcp

Official
by Chia-Network

get_coin_records_by_hints

Read-only

Search for multiple coin records at once using an array of hints, with optional filters for spent status and block height range. Batch replacement for single-hint coin lookups.

Instructions

Find coin records by multiple hints at once. Batch version of get_coin_records_by_hint. Optionally filter by spent status and height range. ⚠️ Coinset-hosted-node extension — not available on a local chia-blockchain node or the simulator.

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": {
      "hints": "<hints>"
    },
    "name": "get_coin_records_by_hints"
  }
}

Input Schema

NameRequiredDescriptionDefault
hintsYesArray of hints to search for (0x-prefixed hex strings)
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

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so safety is covered, and the description adds genuinely new context: the coinset-hosted-node availability restriction, which annotations cannot express. The optional spent-status and height filtering is mentioned but return shape, ordering, and any cap on the number of hints are not disclosed; with no output schema and no stated limits, that leaves a modest gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with purpose and batch scope, then filters, then the availability warning last. Nothing is redundant and no sentence could be removed without losing information.

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?

For a read-only batch lookup with a fully documented schema and no output schema, the description covers identity, relationship to the singular sibling, filter options, and the deployment constraint. It omits what the returned records look like and how the tool behaves on zero matches or very large hint arrays, which is a minor but real omission.

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%, with each of the four parameters already documented in the schema (hints pattern, start/end height semantics, include_spent_coins default). The description's 'filter by spent status and height range' restates the schema rather than adding format or boundary details. Baseline 3 is appropriate when the schema carries the parameter burden.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Find') and resource ('coin records') with an explicit batch scope ('by multiple hints at once'), then anchors it to the singular sibling: 'Batch version of get_coin_records_by_hint.' An agent can distinguish this from get_coin_records_by_hint and from the other lookup siblings without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'batch version of get_coin_records_by_hint' framing tells the agent when to pick this over the single-hint variant, and the deployment constraint ('not available on a local chia-blockchain node or the simulator') is a concrete precondition that governs whether the tool can be called at all. It stops short of explicit when-not-to-use guidance for the other lookup siblings, so not a 5.

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