Skip to main content
Glama

Show container service status and logs

get_app_status
Read-onlyIdempotent

Show the site's container services: per-service status (ready, restarts, waiting or crash reasons, volumes), the stored config, the names of the site secrets that are set (never values) with the dashboard link where the user adds them, the CPU / memory ceilings of this site (resourceCeilings), and optionally the recent logs of one service. Use get_app_status instead of get_site for anything about containers.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_app_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
logsNoService name to include recent logs for (includes the previous crashed container if it restarted).
nameNoSite name as shown by list_sites, e.g. my-portfolio. Provide name or siteId.
tailNoLog lines to return. Default 200.
siteIdNoSite id from list_sites or get_site. Use instead of name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / name / description
      Added value: +"Site name as shown by list_sites, e.g. my-portfolio. Provide name or siteId."
    • addedInput schema / properties / siteId / description
      Added value: +"Site id from list_sites or get_site. Use instead of name."
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds context annotations cannot carry: secrets are returned as names only ("never values") with the dashboard link for adding them, and logs include the previous crashed container after a restart. Those are the two things an agent could otherwise get wrong or over-report.

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?

Front-loaded with the core purpose, then the enumerated payload, then the disambiguation rule last — a sensible order. The main clause is long and list-heavy, but nearly every item maps to something the caller would otherwise have to discover empirically.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the burden of describing return values and does so item by item, including the security-relevant secrets detail. Four fully documented parameters and clear read-only semantics leave nothing an agent needs missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description nudges above it by clarifying that only one service's logs are ever included per call and that ceilings are exposed as resourceCeilings. It does not clarify the name-vs-siteId choice, which the schema handles.

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?

Opens with a specific verb+resource ("Show the site's container services") and enumerates exactly what is returned: per-service status, restart/waiting/crash reasons, volumes, stored config, secret names, resource ceilings, optional logs. The final sentence explicitly separates it from get_site, so an agent can route without opening either schema.

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?

Gives an explicit routing rule — "Use get_app_status instead of get_site for anything about containers" — naming the alternative and the condition that selects it. It also signals that logs are optional and scoped to one service, which tells the agent not to expect all-service logs.

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.