Skip to main content
Glama

Batch Decompile

batch_decompile
Idempotent

Decompile multiple procedure addresses concurrently to recover pseudocode. Preserve each input selector, return ordered per-item success or error results, and report canonical entries and labels.

Instructions

Decompile each explicit procedure symbol or address concurrently. Preserves each input selector in address and reports the observed canonical entry and entry label in procedure; identity or label failures remain explicit without discarding usable pseudocode. Returns ordered per-item success or error results and aggregate counts.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "addresses": []
    },
    "name": "batch_decompile"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressesNoOrdered provider-normalized procedure addresses to analyze.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations, the description discloses meaningful behavior: per-item failures are isolated rather than aborting the batch, usable pseudocode is retained even when identity or label resolution fails, and results come back ordered with aggregate counts. That partial-success contract is exactly the kind of information annotations (readOnly/destructive/idempotent flags) cannot convey. It stops short of stating concurrency limits or how large a batch may be.

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?

Three sentences, front-loaded with the action, then the resilience contract, then the return shape — a sensible ordering with no filler. The phrasing is dense and jargon-forward ('observed canonical entry', 'identity or label failures remain explicit'), which costs some readability but each clause carries real information.

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?

With no output schema, the description must carry the return contract, and it does: ordered per-item success/error entries, the echoed 'address' selector, the resolved 'procedure' entry and label, plus aggregate counts. Combined with idempotentHint and destructiveHint annotations, an agent has enough to call this correctly; only batch-size and timeout behavior are unaddressed.

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% and there is one parameter, so the schema already defines 'addresses' as ordered provider-normalized procedure addresses. The description adds only a small increment — that each input selector is preserved back in an 'address' field and canonicalized into 'procedure' — which mostly describes output rather than enriching the input parameter.

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 names a specific verb ('Decompile') and resource ('each explicit procedure symbol or address') and adds concurrency scope, so the tool's function is unmistakable. It does not, however, contrast itself with plausible siblings such as decompile_subgraph or analyze_function, so an agent must infer the batch-vs-single distinction from the name alone.

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?

Usage is only implied: the phrase 'each explicit procedure symbol or address' signals that this is the multi-selector path, and 'concurrently' hints at bulk work, but there is no explicit when-to-use or when-not-to-use guidance and no named alternative. The agent must decide on its own whether to call this or a single-target decompiler.

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