Skip to main content
Glama
Sign In
Algorand MCP

Algorand MCP

by GoPlausible
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

disassemble_teal

Convert TEAL bytecode back to readable source code for analysis and debugging on the Algorand blockchain.

Instructions

Disassemble TEAL bytecode back to source

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": {
      "bytecode": "<bytecode>"
    },
    "name": "disassemble_teal"
  }
}

Input Schema

NameRequiredDescriptionDefault
bytecodeYesTEAL bytecode to disassemble into source code
networkNoAlgorand network to use (default: mainnet)
itemsPerPageNoNumber of items per page for paginated responses (default: 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.1.1

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the core action but lacks details on permissions, rate limits, side effects, or output format. For a tool that performs a transformation operation, this leaves significant gaps in understanding how it behaves beyond the basic function.

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?

The description is a single, efficient sentence that directly states the tool's function without unnecessary words. It's front-loaded with the core action and resource, making it immediately understandable with zero wasted verbiage.

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?

For a transformation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what format the disassembled source returns in, whether there are any limitations or edge cases, or how the network parameter affects the disassembly process. The minimal description leaves too many operational questions unanswered.

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 fully documents all three parameters. The description doesn't add any parameter-specific information beyond what's already in the schema descriptions, resulting in the baseline score of 3 where the schema does the heavy lifting.

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 verb ('Disassemble') and resource ('TEAL bytecode') with the outcome ('back to source'), making the purpose immediately understandable. However, it doesn't differentiate this tool from potential siblings like 'compile_teal' or other TEAL-related tools in the list, which would require explicit comparison.

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 is provided on when to use this tool versus alternatives. The sibling tools list includes 'compile_teal', which is a logical inverse operation, but the description doesn't mention this relationship or any prerequisites, leaving the agent to infer usage context independently.

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