Skip to main content
Glama

Upstream.codes

Operation status

operation_status
Read-only

Read a durable operation returned by create_repository, import_repository or start_github_sync. Queued or running is not success.

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

Input Schema

NameRequiredDescriptionDefault
ownerYesNamespace that owns the repository (user or organization handle).
operationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuine behavioral value by flagging that queued/running results are not success, which prevents a common agent misread of a status payload. It omits polling cadence and how long operation records remain readable, which is the main remaining gap.

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 zero filler; the resource identification comes first and the constraining caveat second. Nothing could be removed without losing information.

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?

There is no output schema, so the description must carry the return-value burden, and it only partially does: it names non-success states but never enumerates terminal states or what a completed operation record contains. For a polling-style status tool this leaves the agent guessing at the shape of a finished result.

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 coverage is only 50%: owner is documented, while operationId has only a UUID pattern with no prose. The description compensates partially by explaining that the operationId comes from create_repository, import_repository, or start_github_sync, which is real meaning beyond the schema, but it never says where to obtain the owner value or how the pair scopes the lookup.

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?

States a specific verb and resource ("Read a durable operation") and identifies exactly which producing tools return the handle (create_repository, import_repository, start_github_sync). That provenance makes it immediately distinguishable from the read-oriented siblings like get_repository or list_commits.

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?

Usage is clearly implied: call this after one of the three named creation/import tools to check progress, and the sentence "Queued or running is not success" tells the agent not to treat non-terminal states as completion. It stops short of explicit polling guidance or naming a terminal-state check, so it is clear context but not full when/when-not guidance.

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