Skip to main content
Glama
delimit-ai

delimit

Official
by delimit-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Delimit Deploy Status

delimit_deploy_status

Check currently deployed SHA and rollout state for an app environment by reading deploy-system metadata. Answers 'what is live right now?' without probing the running app.

Instructions

Read the current rollout metadata for an app/env (Pro).

When to use: to inspect the currently deployed SHA, rollout state, and any in-progress deploy without actually probing the running app. Useful for "what is live right now?" questions and for the deploy dashboard. When NOT to use: for active runtime health probes (use delimit_deploy_verify), for steady-state observability metrics (delimit_obs_metrics / delimit_obs_status), or to deploy a change (delimit_deploy_plan / delimit_deploy_build).

Sibling contrast: delimit_deploy_verify exercises the running app via probes; this reads deploy-system metadata only. delimit_release_status is the sibling on the release-tracking side (versions, history). Compared to a registry inspection, this reports rollout state, not just image presence.

Side effects: read-only against the deploy backend and gated by require_premium — unlicensed callers receive a license payload and no query runs. On a licensed call, invokes backends.deploy_bridge.status which queries the deploy state store. No write, no probe, no notification. Response routed through _with_next_steps.

Prerequisite: requires Delimit Pro. An unlicensed call returns {"error": ..., "upgrade": "https://delimit.ai/pricing"} without running.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appNoApplication name.
envNoTarget environment.
repo_pathNoExplicit Git worktree root.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv4.13.2
    • addedInput schema / properties / repo_path
      Added value: +{
+  "default": "",
+  "description": "Explicit Git worktree root.",
+  "type": "string"
+}
  2. Changed2 schema fields changedv4.7.9
    • addedInput schema / properties / app / description
      Added value: +"Application name."
    • addedInput schema / properties / env / description
      Added value: +"Target environment."
  3. Changed3 schema fields changedv4.5.5
    • addedInput schema / properties / app / default
      Added value: +""
    • addedInput schema / properties / env / default
      Added value: +""
    • removedInput schema / required
      Removed value: -[
-  "app",
-  "env"
-]
  4. First observedv0.1.0

TDQS

A3.7/5.0
Behavior1/5

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

The description is behaviorally rich, stating read-only behavior, no write/probe/notification, Pro licensing gating, and the internal backend call. However, the annotations declare readOnlyHint=false, which directly contradicts the description's explicit read-only claim. Per the rubric, a description that contradicts annotations receives a score of 1, and this is an annotation contradiction.

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 description is well-structured and front-loaded, with clear sections for purpose, usage, non-usage, sibling contrast, side effects, and prerequisites. It is longer than minimal, but most content earns its place. Minor redundancy exists: Pro licensing is mentioned both as a gating side effect and as a prerequisite, and the registry-inspection contrast is somewhat peripheral.

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?

The description covers use cases, exclusions, licensing prerequisites, side effects, internal behavior, and response routing, while the output schema accounts for return values. It is nearly complete, but the conflicting readOnlyHint annotation leaves the safety profile unreliable, and the optional parameter behavior (especially repo_path) is not elaborated beyond the schema.

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 description coverage is 100%, so the input schema already documents all three parameters. The tool description does not add parameter-level detail beyond the schema, but it does not need to compensate for a coverage gap. Baseline 3 is appropriate.

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?

The description opens with a specific verb and resource: 'Read the current rollout metadata for an app/env.' It then concretely lists what is inspected (deployed SHA, rollout state, in-progress deploy) and contrasts with delimit_deploy_verify and delimit_release_status, making sibling differentiation explicit.

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?

The description provides an explicit 'When to use' section and an equally explicit 'When NOT to use' section, naming exact sibling alternatives such as delimit_deploy_verify, delimit_obs_metrics, delimit_obs_status, delimit_deploy_plan, and delimit_release_status. An agent can determine routing without inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools