Skip to main content
Glama

Show teleprompter

show_teleprompter
Read-onlyIdempotent

Use this when the user wants to read a script in a live teleprompter. Accepts up to 30,000 characters, a whole-number speed from 60 to 300 words per minute or a target duration, text size, mirror mode, and a 0 to 10 second countdown. Returns word count and duration; the full script is shown only in the widget. Numeric pause cues accept whole seconds from 1 to 86,400 per cue. Does not record video or audio.

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": {
      "script": "<script>"
    },
    "name": "show_teleprompter"
  }
}

Input Schema

NameRequiredDescriptionDefault
speedNoOptional whole-number reading speed from 60 to 300 wpm when target_duration_seconds is not used, e.g. 130.
mirrorNoFlip the script horizontally for a glass teleprompter, e.g. true.
scriptYesSpeech script, up to 30,000 characters; numeric pause cues accept whole seconds from 1 to 86,400, e.g. Welcome everyone. [PAUSE 2] Today we will discuss our plan.
text_sizeNoInitial script text size in pixels, e.g. 28.
countdown_secondsNoSeconds to wait after Start before scrolling, e.g. 3.
target_duration_secondsNoOptional desired total duration in seconds including pause cues, e.g. 300.

Output Schema

NameRequiredDescriptionDefault
mirrorYes
durationYes
speed_wpmYes
text_sizeYes
line_countYes
word_countYes
duration_msYes
pause_secondsYes
countdown_secondsYes
target_speed_fractionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds real value beyond that: it discloses that only word count and duration are returned while the full script lives in the widget, and that no video/audio is captured — both non-obvious. It doesn't cover persistence/lifetime of the widget session or whether re-invocation replaces an active session.

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 trigger condition is front-loaded and every sentence carries purpose. Some sentences merely restate numeric bounds that the schema already enforces, which is mild redundancy rather than a structural flaw.

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 an output schema, full parameter descriptions, and rich annotations, the description only needs to fill narrative gaps — and it does: what the user sees, what is returned, that speed may be given as wpm or as a target duration, and that nothing is recorded. An agent has enough to call this correctly.

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 description coverage is 100%, so baseline is 3. The description mostly re-lists constraints already in the schema (30,000 characters, 60–300 wpm, 0–10 second countdown, 1–86,400 second pause cues) and omits the named speed presets (slow/conversational/presentation/fast) that appear in the schema, so it adds little semantic meaning beyond the structured fields.

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 verb and resource ('read a script in a live teleprompter') plus a clear trigger condition, so an agent can tell this launches a display widget rather than computing anything. It also bounds scope with 'Does not record video or audio.' It does not differentiate itself from the siblings estimate_speech_time and plan_script_length, which is the main gap.

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

Usage Guidelines4/5

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

'Use this when the user wants to read a script in a live teleprompter' gives an explicit activation condition. The negative clause rules out recording. However, it never says when to prefer estimate_speech_time or plan_script_length instead (e.g., when the user only wants timing info and no display), so the alternative-routing is left implicit.

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.

Resources