Skip to main content
Glama
Sign In
propresenter-mcp

propresenter-mcp

by Marc416
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

playlists_trigger_previous

Navigate to the previous item in a ProPresenter playlist to control presentation flow during live events or rehearsals.

Instructions

Trigger the previous item in a specific playlist

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": {
      "playlistId": "<playlistId>"
    },
    "name": "playlists_trigger_previous"
  }
}

Input Schema

NameRequiredDescriptionDefault
playlistIdYesThe ID of the playlist

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description must disclose behavior. It only says 'Trigger the previous item' without explaining ordering, wrapping, or side effects. Missing details on what 'previous' means or if it fails at start.

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?

Single concise phrase, front-loaded with action and target. No unnecessary words, but could add more detail without harming conciseness.

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 trigger with one parameter, the description is minimally complete. However, lacks behavioral context like error cases or return values. Acceptable but could improve.

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% (playlistId described). Description adds no additional meaning beyond the schema, so baseline 3 applies.

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 the previous item' and the target 'in a specific playlist'. It distinguishes itself from sibling tools like playlists_trigger_next and playlists_trigger.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives, such as playlists_trigger_previous vs playlists_trigger_next or playlists_trigger. No mention of prerequisites or context.

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