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

stacks-mcp-server

by aibtcdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

search_transactions

Find transactions for a Stacks address. Use optional limit and network parameters to narrow results.

Instructions

Search for transactions by address

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": {
      "address": "<address>"
    },
    "name": "search_transactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of transactions to return
addressYesAddress to search transactions for
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 without disclosing side effects, return format, pagination, or rate limits. Since it is a search, it is implicitly read-only, but there is no explicit statement about behavior beyond the literal action.

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?

The description is a single concise sentence with no wasted words. It effectively front-loads the purpose, though it could have added brief context (e.g., return format) without sacrificing conciseness.

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?

For a simple search tool with full schema coverage, the description provides the minimum viable information. However, it doesn't mention what the response looks like, and with no output schema or annotations, it leaves some ambiguity about the results. It is adequate but not complete.

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 the schema already documents all three parameters (address, limit, network). The description adds no extra meaning beyond the schema, which meets the baseline of 3.

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 the tool's purpose with a specific verb ('Search') and resource ('transactions'), and the key parameter ('by address'). It is distinct from siblings like 'get_transaction_info' which implies a single transaction lookup, though it doesn't explicitly differentiate from them.

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?

There is no guidance on when to use this tool versus alternatives such as 'get_transaction_info' or 'get_account_balance'. The description implies it is for searching by address, but does not state when not to use it or provide context for choosing among siblings.

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