Skip to main content
Glama

Get draft operation status

get_draft_operation
Read-onlyIdempotent

Recover a push_board write or create_version save by operationId. Use the same board you edited.

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": {
      "board": "<board>",
      "operationId": "<operationId>"
    },
    "name": "get_draft_operation"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNowrite: a push_board attempt; save: create_version.write
boardYesYour board: handle/slug or a boardrepo.com URL.
operationIdYesClient-generated UUID. Reuse for retries of the same logical step; use a new one for a new edit or save.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare this is a read-only, idempotent, non-destructive, closed-world retrieval. The description adds meaningful recovery context and a board-matching constraint, but it does not explain error behavior, operation expiration, or how statuses are surfaced beyond what the annotations provide.

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?

Two short sentences with the recovery purpose front-loaded and the critical board constraint immediately after. No wording is wasted.

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 rich annotations, a fully described schema, and an output schema, the description covers the essential calling context. The main remaining gap is routing clarity against get_board_operation, which could prevent wrong-tool selection.

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%, so the schema already fully documents the kind, board, and operationId parameters. The description only reinforces operationId recovery and board matching; it adds little parameter meaning beyond the schema.

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 uses a specific verb ('Recover') and resource ('draft operation') and ties it to the push_board write and create_version save flows. It does not explicitly distinguish itself from the sibling get_board_operation, which leaves some ambiguity about which operation-status tool to use.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly situates usage after a push_board write or create_version save and warns to use the same board that was edited. It stops short of explicitly naming when to use get_board_operation instead or what happens if the board does not match.

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