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

stacks-mcp-server

by aibtcdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

get_transaction_info

Fetch details of a Stacks blockchain transaction by ID, with options to specify the network for accurate lookup.

Instructions

Get information about a transaction by ID

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": {
      "txId": "<txId>"
    },
    "name": "get_transaction_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
txIdYesTransaction ID to look up
networkNoNetwork to querytestnet

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description must carry all behavioral transparency. It only says 'Get information' without disclosing return format, error handling, network behavior, or read-only guarantees. For a potentially complex transaction lookup, this is insufficient.

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?

Single sentence, seven words, front-loaded with the operation. Every word is necessary with no redundancy.

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

Completeness3/5

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

The tool is simple with two parameters and no output schema, but the description doesn't explain what transaction information is returned, network defaults, or behavior when the transaction is not found. This is adequate but leaves gaps for an agent without further context.

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 coverage is 100%, with txId and network both documented in the schema. The description adds no additional parameter semantics, 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 uses a clear verb-resource structure ('Get information about a transaction by ID') and specifies the lookup key. It distinguishes from sibling tools like search_transactions and get_block_info by focusing on a single transaction ID, though it doesn't detail what 'information' includes.

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?

The description implies the tool is used when a transaction ID is known, but doesn't explicitly state when to prefer it over search_transactions or other lookup tools. No alternatives or exclusions are mentioned.

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