Skip to main content
Glama

deploy_status

Read-onlyIdempotent

Read production deploy state on every plan: published state, immutable release, current version and file counts. Preview details require hosted-preview read access. When unavailable, preview_comparison is unavailable and preview comparison values are null; this does not mean the files are in sync. Every production hostname serves the selected production release.

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": {
      "project_id": "<project_id>"
    },
    "name": "deploy_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesProject ID, subdomain, or 'default'.

Output Schema

NameRequiredDescriptionDefault
okNo
dataNo
errorNo
messageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile needs no restating, and the description instead adds a genuine behavioral precondition (hosted-preview read access) plus an anti-footgun: null preview_comparison values do not imply the files are in sync. That is real value beyond the annotations, though it stops short of describing latency, caching, or how production state is refreshed.

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?

The main purpose is front-loaded and each sentence carries a distinct fact: what is returned, the preview access gate, the null-means-not-in-sync warning, and the production hostname note. The closing sentence about production hostnames is slightly cryptic and could be tightened, but there is no filler.

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 an output schema present, return values need no elaboration, and the description covers the one non-obvious behavior: degraded preview data and how to interpret it. For a single-parameter read tool with full annotation coverage, what remains missing (how the two branches differ operationally) is minor.

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 100% for the single project_id parameter, including the accepted 'default' alias, so the schema does the work. The description adds nothing about the parameter, which matches the baseline of 3 when structured fields already cover it.

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 opens with a specific verb and resource ('Read production deploy state on every plan') and enumerates the domain objects it covers: published state, immutable release, current version and file counts. It is clear what a caller gets, though it never names a sibling such as project_deploy or project_deploy_log to delineate the boundary.

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 tool for reading current deploy status, and the preview-access caveat hints at an access precondition. There is no explicit when-to-use versus alternatives guidance, and the sibling list contains deploy-related tools this description does not route away from.

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