Skip to main content
Glama
Averyy

codex-dobby-mcp

by Averyy

reverse_engineer

Investigate binary files using reverse-engineering tools to reveal their structure, behavior, and origins, producing structured investigation results.

Instructions

Use reverse-engineering tooling and broader roots to investigate binaries. Recommended timeout: 30 minutes (1800s).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filesNo
modelNo
dangerNo
promptYes
repo_rootYesAbsolute path to the target git worktree. Always pass the caller's active repository root; Dobby deliberately has no implicit repo fallback.
extra_rootsNo
timeout_secondsNo
reasoning_effortNo
important_contextNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
toolYes
modelYes
statusYes
summaryYes
task_idYes
warningsNo
exit_codeNo
repo_rootYes
file_diffsNo
next_stepsNo
duration_msNo
stop_reasonNo
completenessYes
result_stateNofinal
files_changedNo
artifact_pathsYes
review_detailsNo
important_factsNo
reasoning_effortYes
sandbox_violationsNo
raw_output_availableNo
reverse_engineer_detailsNo
Behavior2/5

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

No annotations are present, so the full burden is on the description. It does not disclose whether the tool is read-only, what side effects exist, or what kind of output to expect. The only behavioral hint is the recommended timeout.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short, but the phrase 'broader roots' is unclear and wastes space. The timeout recommendation is useful but could be integrated more elegantly. The description is not front-loaded with the most critical information.

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?

Given the tool's complexity (9 parameters, required prompt and repo_root) and lack of output schema details, the description is insufficient. It does not explain what the tool returns or how to interpret results, leaving the agent underinformed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 11% (only repo_root is described). The tool description does not explain any of the 9 parameters, leaving their purposes largely undefined. The agent would have no way to understand parameters like 'extra_roots' or 'important_context' without additional context.

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 investigates binaries using reverse-engineering tooling. It is specific about the resource (binaries) and the action (investigate). However, the phrase 'broader roots' is vague and does not add clarity.

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?

The description mentions a recommended timeout but gives no guidance on when to use this tool vs sibling tools (e.g., research, review). No context about prerequisites or typical scenarios is provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Averyy/codex-dobby-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server