Skip to main content
Glama
chia-mcp

chia-mcp

Official
by Chia-Network

get_coin_records_by_names

Read-only

Fetch multiple Chia coin records by their 0x-prefixed coin IDs in one batch, with optional filters for spent status and creation height range.

Instructions

Get multiple coin records by their coin IDs. Batch version of get_coin_record_by_name. 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": {
      "names": "<names>"
    },
    "name": "get_coin_records_by_names"
  }
}

Input Schema

NameRequiredDescriptionDefault
namesYesArray of coin IDs to look up (0x-prefixed, 32 bytes hex each)
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/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the main safety profile is covered. The description adds that filtering by spent status and height range is optional, but it does not disclose ordering, missing-coin behavior, or other response characteristics.

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?

Three short sentences, front-loaded with the core operation, then the sibling comparison, then the optional filters. Nothing is wasted and the structure is easy to scan.

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 full parameter schema descriptions and no output schema, the definition provides the essential purpose and filter context. It could be slightly more complete by mentioning how unknown or missing coin IDs are handled.

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 all four parameters are already documented in the input schema. The description only names the spent-status and height-range filters without adding syntax or constraints beyond the schema.

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 and resource ('Get multiple coin records by their coin IDs') and explicitly distinguishes the batch operation from the singular sibling get_coin_record_by_name.

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 phrase 'Batch version of get_coin_record_by_name' gives clear context for choosing this tool over the single-record sibling, but it does not mention whether other lookup methods such as puzzle hash or hint queries might be more appropriate when available.

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