Skip to main content
Glama
Sign In
stacks-mcp-server

stacks-mcp-server

by aibtcdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

get_network_status

Get current network status and blockchain information for Stacks mainnet, testnet, or mocknet.

Instructions

Get current network status and blockchain information

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_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
networkNoNetwork to querytestnet

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only states the action and resource, but does not disclose what 'blockchain information' includes, how network affects output, or any side effects. It is safe to assume read-only, but no explicit detail is given.

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?

One concise sentence front-loads the purpose. No wordiness, though it could be more informative without losing conciseness.

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

Completeness2/5

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

The tool has no output schema, so the description should explain what return information is provided. It only says 'blockchain information', which is vague. Also, the potential confusion with check_api_status is not resolved. Despite simplicity, it's incomplete for practical use.

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 a clear description 'Network to query' and enum values. The description adds no extra meaning beyond the schema, so baseline 3 applies.

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 a 'Get' action on 'network status and blockchain information', which is specific and distinct from siblings like check_api_status. However, it does not explicitly differentiate from similar tools.

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?

No guidance on when to use this tool vs alternatives like check_api_status, or any context such as network availability or when blockchain information is needed. No exclusion criteria or alternative mentions.

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

Deploy Server

Other Tools