Skip to main content
Glama
chia-mcp

chia-mcp

Official
by Chia-Network

get_network_info

Read-only

Retrieve the connected Chia node's network name and address prefix (e.g., mainnet, xch) to identify the active network before building or validating addresses.

Instructions

Get the network name and address prefix for the connected Chia node. Returns the network name (e.g., 'mainnet') and prefix (e.g., 'xch').

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A3.6/5.0
Behavior4/5

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

With only readOnlyHint=true in annotations, the description usefully adds that the query targets the connected node and describes the exact return payload (network name like 'mainnet', prefix like 'xch'). This is meaningful disclosure beyond the annotation, and no contradictions exist. It stops short of noting failure behavior when no node is connected.

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?

Two short sentences, front-loaded with the action and scope. The second sentence largely restates the first's 'network name and address prefix' phrase, though the concrete examples add value, so it is slightly redundant but not wasteful.

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 simple, zero-parameter read with no output schema, the description covers what is returned and in roughly what shape, which is the main thing an agent needs. Only the behavior on an unreachable node is left unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the schema is trivially complete. Baseline 4 applies for a no-argument tool.

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?

States a specific verb and resource ('Get the network name and address prefix for the connected Chia node'), so an agent knows exactly what information is retrieved. It does not distinguish itself from broader state tools such as get_blockchain_state, but the resource is narrow enough to be unambiguous.

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

Usage Guidelines2/5

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

The description never says when to call this instead of alternatives (e.g., get_blockchain_state, which likely also exposes network identity). It gives only implied usage: 'if you need the network name or prefix.' No prerequisites, exclusions, or sibling routing are provided.

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