Skip to main content
Glama

Get demo diagnostics

get_demo_diagnostics
Read-only

Read one Application demo's tracked record (status, kind, branch or pr_number, image tag, container port, last_error, preview URL, expiry) plus a bounded log tail of the demo container's most recent start attempt - on a crash-looping container the tail shows the crashed attempt's output, which usually names exactly which environment variables the application demands. Use this for a crash-looping or failed demo (CrashLoopBackOff, a container that exits at startup, status failed) before changing its configuration. For 'the preview does not load / does not resolve / certificate error' start with inspect_demo instead: it reads the live namespace inventory and probes the URL, which this tool does not. Identify the demo by workspace_id or namespace (list_application_demos shows both).

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": "get_demo_diagnostics"
  }
}

Input Schema

NameRequiredDescriptionDefault
namespaceNoThe demo namespace (ankra-demo-pr-* / ankra-demo-br-*). Optional if workspace_id is given.
tail_linesNoLog lines to tail from the demo container (default 200).
workspace_idNoThe demo's workspace id. Optional if namespace is given.
application_idYesThe Application whose demo to diagnose.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true and the title; the description adds the substantive behavior — that the tail is bounded and covers the most recent start attempt, that on a crash-looping container it surfaces the crashed attempt's output which typically names the missing environment variables, and that the tool does not read the live namespace inventory nor probe the URL. That scope boundary is exactly the kind of disclosure annotations cannot carry.

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 resource and return payload, then usage, then exclusion, then identification — a sensible order. The single-sentence field enumeration with a parenthetical list is dense but every clause carries information; only the trailing identification reminder is close to redundant with the schema.

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?

There is no output schema, so the description must describe the return value, and it does so field by field while explaining the diagnostic significance of the log tail. For a read-only four-parameter diagnostic tool it leaves nothing an agent needs before calling it or before interpreting the result.

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% and it already states that workspace_id and namespace are mutually optional, so the description's baseline would be 3. It adds a discovery path — both identifiers come from list_application_demos — which meaningfully shortens the lookup loop, though it does not explain tail_lines sizing or what happens when both identifiers are supplied.

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 (read one Application demo's tracked record) and enumerates exactly what comes back: status, kind, branch or pr_number, image tag, container port, last_error, preview URL, expiry, plus a bounded log tail. It also names the sibling it is not (inspect_demo) and the discovery sibling (list_application_demos), so an agent can distinguish it without opening any 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 when-to-use condition (CrashLoopBackOff, container exiting at startup, status failed) and an explicit when-not with the named alternative (preview does not load / does not resolve / certificate error → inspect_demo, because it reads live namespace inventory and probes the URL). It also states the sequencing rule: do this before changing configuration.

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.