Skip to main content
Glama
Sign In
propresenter-mcp

propresenter-mcp

by alxpark
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

clear_trigger_group

Triggers a specific clear group by its ID to manage ProPresenter presentation elements.

Instructions

Trigger a specific clear group

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": "clear_trigger_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe ID of the clear group to trigger

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.5/5.0
Behavior2/5

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

No annotations provided, and the description does not disclose any behavioral traits such as whether the action is destructive, side effects, or required permissions. The phrase 'Trigger a specific clear group' is too vague to understand the tool's behavior.

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

Conciseness3/5

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

The description is a single sentence, concise, but lacks substance. It is front-loaded but does not earn its place by adding value.

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 the complexity of the sibling tools and lack of annotations/output schema, the description fails to provide critical context about what 'trigger' means, how 'clear group' relates to other groups, and the effect of the action.

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% and the description adds no additional meaning beyond the schema's parameter description. Baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses verb 'Trigger' and resource 'clear group', but it's vague about what 'trigger' means in this context. It does not distinguish from similar sibling tools like 'trigger_active_group' or 'trigger_presentation_group', nor from 'clear_layer'.

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 vs alternatives. There are many sibling tools with similar actions, but the description provides no context for selection.

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