Skip to main content
Glama
Sign In
propresenter-mcp

propresenter-mcp

by Marc416
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

props_pause_auto_clear

Pause automatic clearing for a specific prop in ProPresenter to maintain its display during presentations without manual intervention.

Instructions

Pause auto-clear for a specific prop

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": {
      "id": "<id>"
    },
    "name": "props_pause_auto_clear"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe ID of the prop

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 behavioral traits. It only states 'pause auto-clear' without explaining what happens to the current state, whether the effect is reversible, or any side effects. This is insufficient for safe agent usage.

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 sentence with no wasted words. It is appropriately concise for a tool with a single parameter and straightforward action.

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?

Given no output schema and no annotations, the description should provide more context. It does not explain what 'auto-clear' means, what pausing entails, or any return value. The minimal description is inadequate for a complete understanding.

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 description for the 'id' parameter. The tool description adds no extra meaning beyond 'specific prop', which is already implied. Baseline score of 3 is appropriate as the schema does the heavy lifting.

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 specific action ('pause auto-clear') and the resource ('a specific prop'), distinguishing it from siblings like 'props_resume_auto_clear' and 'props_clear'. It uses a specific verb and noun.

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 alternatives (e.g., 'props_clear' or 'props_resume_auto_clear'). There is no mention of prerequisites, context, or when pausing auto-clear is appropriate.

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