Skip to main content
Glama

Inspect demo

inspect_demo
Read-only

The first call for any question about an Application demo or preview that does not work, does not load, times out, shows a certificate error, or says ready but cannot be opened. One call reads the demo record, the live state of its namespace on the staging cluster reduced to what decides reachability (deployment ready/desired counts, pod container waiting and terminated reasons with restarts, service selector and ready endpoint count, ingress hosts, address and TLS secret, cert-manager certificate readiness when present, the newest Warning events), probes the preview URL live from the Ankra platform (reachable, failure_stage dns/connect/timeout, HTTP status, resolved IP, TLS verified/issuer/days_until_expiry), and returns a verdict naming the first broken hop in plain words (for example 'hostname does not resolve (NXDOMAIN); the workload is healthy'). Answer from the verdict; do not re-read pods, services, ingresses or events yourself. read_failures lists what could not be read, so an empty inventory list means absent only when read_failures is empty. Identify the demo by workspace_id, namespace or preview_url (any one; list_application_demos shows all three). For a crash-looping container follow up with get_demo_diagnostics for the log tail. 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": "inspect_demo"
  }
}

Input Schema

NameRequiredDescriptionDefault
namespaceNoThe demo namespace (ankra-demo-pr-* / ankra-demo-br-*). Optional if workspace_id or preview_url is given.
preview_urlNoThe preview URL or hostname the user is trying to open, matched against the demo's recorded preview_url. Optional if workspace_id or namespace is given.
workspace_idNoThe demo's workspace id. Optional if namespace or preview_url is given.
application_idYesThe Application whose demo to inspect.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint annotation: it describes exactly what is read (demo record, namespace reachability signals, live URL probe with failure_stage/HTTP/TLS fields) and that a plain-words verdict naming the first broken hop is returned. It also discloses a subtle behavioral rule (read_failures must be empty before treating an empty inventory as absent) and reinforces the read-only nature, consistent with annotations.

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?

Dense and front-loaded with the purpose before the mechanics, and every clause carries information (reachability signals, probe outputs, verdict, read_failures caveat, identifier choice, follow-up tool). It loses a point for packing large amounts of detail into very long compound sentences that are harder to scan than a short structured list would be.

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?

For a complex, multi-source diagnostic tool with no output schema and only a readOnly hint, the description covers what is read, what the verdict contains, how failures surface (read_failures), how to identify the demo, and when to branch to get_demo_diagnostics. Nothing an agent needs to call it correctly appears missing.

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%, so per the baseline this is a 3. The description adds real value by saying the demo can be identified by workspace_id, namespace, or preview_url (any one) and pointing to list_application_demos for discovery. However it entirely omits application_id, which the schema marks as REQUIRED, creating a mismatch that leaves the actual mandatory identifier unexplained.

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 (inspect/read + probe + return verdict) and resource (Application demo/preview) and scopes the trigger conditions precisely (does not work, times out, cert error, ready-but-unopenable). It distinguishes itself from siblings by naming list_application_demos and get_demo_diagnostics and by explicitly telling the agent not to re-read pods/services/ingresses/events.

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 this is the FIRST call for demo-related failures and enumerates the failure classes that select it. It names the follow-up alternative (get_demo_diagnostics for crash-looping containers) and the discovery tool (list_application_demos), leaving little to inference.

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.