Skip to main content
Glama
Sign In
propresenter-mcp

propresenter-mcp

by Marc416
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

trigger_presentation_previous

Navigate to the previous cue in a ProPresenter presentation using its UUID to control presentation flow during live events or rehearsals.

Instructions

Trigger the previous cue in a specific presentation by UUID

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": {
      "presentationUuid": "<presentationUuid>"
    },
    "name": "trigger_presentation_previous"
  }
}

Input Schema

NameRequiredDescriptionDefault
presentationUuidYesThe UUID of the presentation

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states the action, omitting any details about side effects (e.g., advancing slide, mutating state), prerequisites (e.g., presentation must be active), or error conditions. Minimal transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, concise sentence that front-loads the essential information. Every word contributes meaning, with no wasted text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter trigger tool without an output schema, the description adequately conveys the core function. However, it lacks any behavioral context or return value information, leaving the agent underinformed for non-trivial usage scenarios.

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?

The input schema has 100% coverage with a single parameter 'presentationUuid' described as 'The UUID of the presentation'. The description adds no extra meaning beyond what the schema provides, earning the baseline score of 3.

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 clearly states the action (trigger), target (previous cue), and scope (specific presentation by UUID). It differentiates from siblings like trigger_presentation_next or trigger_focused_previous by specifying 'previous cue' and the UUID requirement.

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?

The description implies usage: trigger the previous cue in a specific presentation. However, it does not provide explicit guidance on when to use this tool versus alternatives like trigger_focused_previous or trigger_previous_slide, leaving the agent to infer from the name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools