Skip to main content
Glama
Sign In
propresenter-mcp

propresenter-mcp

by Marc416
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

timers_operation

Control ProPresenter timers by starting, stopping, or resetting them using timer IDs for presentation automation.

Instructions

Perform a specific operation on a timer (start, stop, reset)

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": {
      "timerId": "<timerId>",
      "operation": "<operation>"
    },
    "name": "timers_operation"
  }
}

Input Schema

NameRequiredDescriptionDefault
timerIdYesThe ID of the timer
operationYesThe operation to perform: start, stop, or reset

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description must bear the full burden of behavioral disclosure. It only repeats the operation and resource, omitting key details like side effects (e.g., state changes), prerequisites (e.g., timer existence), and response behavior. The behavioral transparency is insufficient for confident invocation.

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, brief sentence that efficiently conveys the core purpose. It is front-loaded with the key action and examples, containing no extraneous words. This is ideal for AI parsing.

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

Completeness2/5

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

The tool is simple but lacks explanation of return values (no output schema) and fails to address when to use this unified operation over individual tools. The description is too minimal to be fully self-contained for an AI agent, especially given the absence of annotations.

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 provides 100% coverage with clear descriptions for both parameters ('timerId', 'operation'). The description adds no new semantic information beyond the schema, so it meets the baseline expectation but does not enhance understanding.

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?

The description clearly states the verb 'perform operation' and the resource 'timer' with explicit examples (start, stop, reset). However, among sibling tools like 'timers_start', 'timers_stop', and 'timers_reset', which perform the same individual operations, this tool's description does not differentiate it, missing a chance to clarify its role as a unified alternative.

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 is provided on when to use this tool versus the more specific sibling tools (e.g., 'timers_start', 'timers_stop', 'timers_reset'). The description gives no context about prerequisites, alternatives, or whether this tool is intended for programmatic use where the operation is dynamic.

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