Skip to main content
Glama

AppDeploy

by ai.appdeploy
OverviewDiscussionsAdmin

Get app status

get_app_status
Read-onlyIdempotent

Use this when deploy_app returns, when checking deployment status, or when the app has errors or is not working as expected. Returns deployment status, e2e test status, QA snapshot, and frontend/backend error logs; treat deployed_and_testing status as non-final, always inspect QA/errors, and call get_e2e_qa_run_details if e2e tests fail.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoOptional shared cap for returned logs across frontend and backend combined. Defaults to 50 when omitted.
sinceNoOptional timestamp in epoch milliseconds to filter errors. When provided, returns only errors since that timestamp.
app_idYesTarget app id
resources_onlyNoRead the app's resource slots and uploaded paths without polling QA or starting a deployment.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / resources_only / description
      Previous value: -"Read resource slots and uploaded paths without polling QA or deploying code."New value: +"Read the app's resource slots and uploaded paths without polling QA or starting a deployment."
  2. Changed1 schema field changed
    • changedInput schema / properties / resources_only / description
      Previous value: -"Read the app's resource slots and uploaded paths without polling QA or starting a deployment."New value: +"Read resource slots and uploaded paths without polling QA or deploying code."
  3. Changed1 schema field changed
    • addedInput schema / properties / resources_only
      Added value: +{
+  "description": "Read the app's resource slots and uploaded paths without polling QA or starting a deployment.",
+  "type": "boolean"
+}
  4. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description does not need to restate safety. It adds valuable behavioral context: 'treat deployed_and_testing status as non-final' and 'always inspect QA/errors', which are non-obvious operational instructions beyond the annotations. It stops short of explaining pagination semantics or return shape, but the guidance is strong.

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?

The description is two sentences, front-loaded with the primary trigger and then the return contents. Every clause (status interpretation, QA inspection, follow-up tool) earns its place; 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?

For a read-only status tool with full schema coverage and no output schema, the description is nearly complete: it states triggers, return fields, interpretation rules, and a follow-up path. The only minor gap is that the exact structure of the returned QA snapshot is not described, but that is acceptable for a summary tool.

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 baseline is 3. The description does not add meaning beyond the schema for app_id, limit, since, or resources_only; all parameter semantics are already fully documented in the schema.

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 ('get app status') and enumerates exactly what is returned: deployment status, e2e test status, QA snapshot, and error logs. This clearly distinguishes it from siblings like get_app_versions or deploy_app.

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?

Explicitly says when to use: 'when deploy_app returns', 'when checking deployment status', or 'when the app has errors or is not working as expected'. It also names an alternative for a specific follow-up ('call get_e2e_qa_run_details if e2e tests fail'), giving both trigger conditions and routing guidance.

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

All AppDeploy toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources