Skip to main content
Glama

List application demos

list_application_demos
Read-only

List an Application's active demos (PR and branch previews): for each, workspace_id, kind, branch or pr_number, namespace, status, preview_url with any recorded preview_unreachable_reason, last_error, created_at and expires_at, plus the staging cluster and whether its agent is online. Use this when the user names an application but not which demo or preview they mean, or asks whether a demo exists or is still running - then pass the workspace_id, namespace or preview_url to inspect_demo. Never search namespaces across clusters to find a demo. Read-only.

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": {
      "application_id": "<application_id>"
    },
    "name": "list_application_demos"
  }
}

Input Schema

NameRequiredDescriptionDefault
application_idYesThe Application whose demos to list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The readOnlyHint annotation already establishes the safety profile, and the description confirms it with 'Read-only' while adding real context: which fields come back (status, preview_url, preview_unreachable_reason, last_error, expires_at) and that staging cluster agent liveness is included. It stops short of covering result volume, ordering, or pagination, so it enriches behavior without fully describing the response shape.

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 list of returned fields is front-loaded in the first sentence and the routing guidance follows, so an agent can stop reading early if it only needs purpose. The field enumeration is a long run-on that could be tightened, but every element carries information an agent needs to interpret the results.

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 no output schema, the description correctly compensates by enumerating returned fields and their meaning, including failure signals like preview_unreachable_reason and last_error. What remains unaddressed is edge-case behavior such as an empty result set or how many demos are returned, which is a minor gap for a single-parameter read 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 coverage is 100% and the single application_id parameter is already documented as 'The Application whose demos to list', so the description adds little new meaning about the parameter itself. The mention of workspace_id, namespace, and preview_url refers to inputs for the downstream inspect_demo call, not to this tool's own parameter, keeping this at the baseline for a fully documented 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?

The description opens with a precise verb and resource scope: 'List an Application's active demos (PR and branch previews)', then defines what each demo record contains. It is immediately distinguishable from sibling tools like inspect_demo, demo_stop, and redeploy_demo because it is the enumeration step, not the inspect or mutate step.

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?

It states exactly when to reach for it ('when the user names an application but not which demo or preview they mean, or asks whether a demo exists or is still running') and names the follow-up alternative with the inputs to hand it ('pass the workspace_id, namespace or preview_url to inspect_demo'). It also gives an explicit prohibition: 'Never search namespaces across clusters to find a demo.'

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.