Skip to main content
Glama

Get deployment

get_deployment
Read-onlyIdempotent

Get deployment status (BUILDING → LIVE / FAILED). site_url is the website; backends lists each server service's own URL.

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"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idNoProject id (or use session from use_project)
deployment_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds real value beyond that by explaining the state transition model a caller will observe and by naming two returned fields (site_url, backends) with a pointed clarification that each backend has its own URL — genuinely useful since no output schema exists.

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?

Two tight sentences with no filler, and the state-machine detail is front-loaded. The second sentence reads slightly unframed — it is about return values but never says so — which costs it a perfect score.

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 simple, read-only getter with two parameters and no output schema, the description covers the operation and two of the salient return fields. It is nearly complete; the only real hole is the undocumented deployment_id parameter and the absence of any pointer to the listing alternative.

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?

Schema coverage is only 50%: deployment_id has no schema description at all, and the description never explains it, nor does it clarify the interaction between project_id and the session-based default. The two fields it does explain (site_url, backends) are outputs, not parameters, so they do not compensate for the parameter gap.

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 (get deployment status) and adds the meaningful domain detail of the BUILDING → LIVE / FAILED lifecycle, which tells the agent what a single deployment record represents. It does not explicitly distinguish itself from the sibling list_deployments, so it falls short of a 5.

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?

Usage is only implied: an agent can infer this is the single-deployment lookup versus the list tool, but the description never states when to prefer it, nor when to use get_status/get_services instead. No prerequisites or exclusions are mentioned.

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