Skip to main content
Glama

Get an edit

get_edit
Read-only

Status of an edit (pass wait_seconds up to 50 to wait until ready). When ready, result_url downloads the edited PNG for one hour. Free.

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": {
      "edit_id": "<edit_id>"
    },
    "name": "get_edit"
  }
}

Input Schema

NameRequiredDescriptionDefault
edit_idYesThe id returned by replace_text.
wait_secondsNoHow long to wait for the result before returning, 0 to 50 seconds.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations only declare that this is a safe, closed read; the description adds two things the schema cannot express: the result_url is time-limited to one hour, and the call is free. That gives valuable operational context, although the actual status values that can be returned (pending, failed, etc.) are never described.

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?

Three short sentences that front-load the core action, then the readiness mechanism, then the payoff and cost. No filler, no redundancy, and the parenthetical keeps the waiting hint adjacent to the action it modifies.

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?

For a two-parameter read tool with full schema coverage and annotations covering the safety profile, the description covers the essentials: what it returns, how long the URL lasts, and the cost. It falls just short because it does not explain the non-ready case or what the status field contains.

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%; both parameters are already documented, including edit_id's provenance from replace_text and wait_seconds' 0–50 range. The description restates the wait behavior but adds no new syntax or meaning beyond the schema, so a baseline 3 is appropriate.

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-and-resource combination (get the status of an edit) and immediately follows with the outcome (result_url downloads the edited PNG). The reference to replace_text ties it to the workflow that produces an edit_id, which effectively sets it apart from get_credits and scan_text, even though no sibling is explicitly named.

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 description implies the main usage pattern by suggesting that you pass wait_seconds 'up to 50 to wait until ready,' which tells the agent to poll or block rather than guess. However, it never states when to call this instead of a sibling, nor what to do when the status is not ready.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources