Skip to main content
Glama

export

Generates patch files in IPS or XDelta format and trainer tables from paths, and retrieves changelogs or job logs by module and action.

Instructions

Export patches/tables. Dispatches by module+action.

Modules/actions: patch: export_patch (original_path, modified_path, out_path, fmt=ips|xdelta) patch: make_trainer_table (addresses, out_path) diagnose: changelog joblog: list

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": "export"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
moduleYes
paramsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 behavioral burden. It discloses the dispatch mechanism and that operations write to an 'out_path', but says nothing about overwriting existing files, required permissions, failure modes, or whether outputs are deterministic — significant gaps for a tool that produces artifacts on disk.

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 one-line purpose followed by a compact indented menu; almost no filler. Minor cost: entries like 'joblog: list' and 'diagnose: changelog' are so terse that their parameters and purpose are left implicit.

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?

An output schema exists, so return values need not be explained, and the listed actions are reasonably covered. However, for a free-form dispatcher it never states whether the module/action list is exhaustive, how unknown modules are handled, or what happens on partial failures — gaps an agent would hit immediately.

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 0% and the top-level 'params' object is an untyped additionalProperties bag, so the description is the only documentation of what belongs inside it. It does name the expected keys per action and supplies the only enum information available (fmt=ips|xdelta), but it omits types, path format expectations, and what 'addresses' should look like.

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 opens with a specific verb and resource ('Export patches/tables') and then enumerates concrete module/action pairs, so an agent can tell this is the export dispatcher rather than edit, inspect, or validate. It stops short of a 5 because the enumeration is presented without any statement that it is the authoritative set of supported operations.

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 list implies how to invoke the tool for each export case, which is useful routing information, but there is no explicit when-to-use versus when-to-use-a-sibling guidance (e.g. export vs inspect or validate). Usage is implied rather than stated.

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