Skip to main content
Glama

edit

Modify files and structures via module/action dispatch, supporting hex and APK patches, table entry/field changes, offset rebuilds, checksum fixes, and template writes with dry-run.

Instructions

Edit files/structures. Dispatches by module+action. Supports dry_run.

Modules/actions: hex: hex_patch (path, offset, bytes_hex, dry_run) apk: smali_patch (src_dir, file_rel, old, new, dry_run) tables: clone_entry, edit_fields, rebuild_offsets, checksum_fix format: write_template Every write snapshots first and logs to job_log.

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": {
      "module": "<module>",
      "action": "<action>"
    },
    "name": "edit"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
moduleYes
paramsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations the description carries the full burden, and it does add real behavioral value: writes are preceded by a snapshot and logged to job_log, and dry_run is supported. However it never states whether the original file is mutated in place, whether the snapshot is restorable (an undo sibling exists but is not referenced), permission/auth needs, or failure behavior.

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?

Front-loaded with the core statement and two key behaviors, then a compact structured list; nearly every line earns its place. The catalog is terse to the point where several listed actions carry no useful detail, which is brevity at the cost of clarity.

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 mutation dispatcher with no annotations and an output schema (so return values needn't be explained), the definition covers safety and dry_run but leaves the tables and format actions with no parameter or effect information, and gives no cross-tool routing. Adequate to start, incomplete for several of the advertised actions.

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

Parameters4/5

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

Schema coverage is 0% and the free-form 'params' object is completely opaque in the schema, so the description's per-module parameter lists (path/offset/bytes_hex, src_dir/file_rel/old/new) are the primary source of meaning. It stops short of giving any parameter detail for the tables actions or format.write_template, and never documents the legal values of 'module' or 'action' explicitly as enums.

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?

States a specific verb ("Edit") plus resource ("files/structures") and immediately discloses the dispatch mechanism by module+action, then enumerates the actual capabilities (hex_patch, smali_patch, table ops, write_template). It does not differentiate against overlapping siblings such as patch_code or rebuild, so an agent can't fully infer which tool to pick from this description 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?

The module/action catalog implies the usage space and shows where each capability lives, but there is no explicit when-to-use guidance, no exclusions, and no prerequisites (e.g., when to use edit vs patch_code/rebuild). Choosing the right module is left to inference from the action names.

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