Skip to main content
Glama

Check deployment

get_deployment_status
Read-onlyIdempotent

Returns an authorized deployment’s durable status, processing logs, release ID, public URL, failure guidance and original publication revision when available.

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": {
      "deployment_id": "<deployment_id>"
    },
    "name": "get_deployment_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
deployment_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value by enumerating the returned fields and flagging that the revision is only present 'when available', implying nullable response fields. It does not explain what status values mean or whether failures surface as an error or as data.

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?

One front-loaded sentence that starts with the verb and spends no words on preamble. The list of returned fields is compact and scannable, though slightly long and lacking any structural separation for the return values.

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?

No output schema exists, so the field enumeration does essential work and is reasonably complete for a point-read status tool. The main gap is the absence of any parameter detail or explanation of failure semantics. For a one-parameter read, it is close to sufficient overall.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter has 0% schema description coverage, so the description carries the whole burden, and it explains nothing about deployment_id. It does not mention the required 'dep_'/'rjob_' prefix pattern or that the deployment must be one the caller is authorized to read; 'authorized' is the only hint. With one undocumented parameter, a low score is warranted.

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?

States a specific verb and resource: returns a deployment's status plus a precise list of fields (durable status, processing logs, release ID, public URL, failure guidance, publication revision). An agent can distinguish it from get_deployment_changes, which clearly targets change data rather than status. It stops short of explicitly naming a sibling alternative, so it is clear but not fully differentiated.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance is given; the description never says to call this after begin_deployment/finalize_deployment or instead of list_releases. The context is only inferable from the tool name and the required deployment_id parameter. It also never states prerequisites such as needing an authorized deployment.

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