Skip to main content
Glama

Check a new demo’s progress

get_demo_progress
Read-onlyIdempotent

How a demo made with create_demo is coming along: the pages being captured (each one’s status, title or why it failed), whether the demo exists yet (demoReady), and the AI pass writing its copy and voice (per part: copy, narration scripts, voice clips; notes say why a part was skipped, e.g. no AI credits left or voice not on this plan). Works for any demo’s latest AI pass too.

Requires: demos:read.

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": {
      "demoId": "<demoId>"
    },
    "name": "get_demo_progress"
  }
}

Input Schema

NameRequiredDescriptionDefault
demoIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare a read-only, idempotent, non-destructive operation, so the bar is low, but the description adds real context: it is a status/polling surface, it reports failure reasons per page, and it explains why AI parts get skipped (no credits, voice not on plan). It also discloses the required scope `demos:read`, which no annotation provides.

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-loads the core purpose and keeps everything in two sentences plus a scope line, with no filler. The heavy parenthetical nesting makes it dense to parse, but each clause carries information an agent would otherwise lack.

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 and only one parameter, so the description carries the return-value burden and does so thoroughly: page statuses, readiness flag, per-part copy/script/voice status, and skip notes. Combined with the disclosed permission scope, an agent has enough to call it and interpret the result.

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 0% for the single `demoId` parameter, so the description must compensate. It hints the ID originates from `create_demo`, which is useful, but it does not state the accepted ID format or other sourcing (e.g., `list_demos`), leaving the sole input under-explained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource and a clear read purpose: demo progress, covering page-capture statuses, `demoReady`, and the state of the AI copy/voice pass. It ties itself to `create_demo` output but never contrasts with `get_demo`, so an agent must infer the boundary between the two.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies the when: poll this after calling `create_demo`, and it notes it also works for any demo's latest AI pass. There is no explicit when-not and no named alternative (e.g., use `get_demo` for the demo record itself), so routing guidance is only implied.

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.