Skip to main content
Glama

Get board save or remix status

get_board_operation
Read-onlyIdempotent

Follow an MCP save or remix by its original operationId, scoped to your personal workspace. An upload reports unknown, pending, retry, failed or committed. A remix is committed as soon as remix_board answers; filesCopying reports background copy progress. Retry means no request owns the operation now: call commit_board_upload again with the same upload and operation ID. Unknown can mean preparation completed but commit never started: retry the same commit, not a new project. Committed returns canonical owner URLs without share credentials. Returns current rendering status separately; review is not implied. This tool remains available with own-board read access when publishing is disabled.

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

Input Schema

NameRequiredDescriptionDefault
operationIdYesA client-generated UUID. Reuse it for all retries of this exact upload; never reuse it for different files or metadata.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the bar is lower, yet the description adds real behavior: state meanings, that filesCopying reports background copy progress, that committed returns canonical owner URLs without share credentials, and that the tool remains available with own-board read access when publishing is disabled. The only gap is no mention of polling cadence or terminal-state detection guidance, which matters for a status-check tool.

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 purpose followed by state semantics, and nearly every sentence adds distinct operational meaning. The prose is dense and semicolon-heavy, with some run-on constructions ('Unknown can mean preparation completed but commit never started: retry the same commit, not a new project') that could be split for faster scanning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 shape needn't be described, and the description still covers the state vocabulary, the copy-progress field, the URL/credential behavior on success, and permission/availability caveats. For a one-parameter status-polling tool this is complete.

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 100% and the schema already explains UUID reuse for retries, so the baseline is 3. The description adds a small but meaningful disambiguation by specifying the 'original operationId', clarifying which ID to follow after a retry, which is the one genuinely ambiguous aspect of a single-UUID tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb+resource: 'Follow an MCP save or remix by its original operationId, scoped to your personal workspace.' It enumerates the status vocabulary (unknown, pending, retry, failed, committed) and distinguishes this from remix_board and commit_board_upload by naming them, so an agent can select it without opening sibling schemas.

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

Usage Guidelines5/5

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

Gives explicit when-and-what-to-do: Retry status means 'call commit_board_upload again with the same upload and operation ID', and Unknown means 'retry the same commit, not a new project'. It also states a scope exclusion ('scoped to your personal workspace') and clarifies that review is not implied, leaving little to inference.

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