Skip to main content
Glama
Sign In
propresenter-mcp

propresenter-mcp

by Marc416
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

status_post_updates

Subscribe to real-time status updates from ProPresenter to monitor presentation changes and system events as they occur.

Instructions

Subscribe to status updates with specific configuration

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": {
      "updates": "<updates>"
    },
    "name": "status_post_updates"
  }
}

Input Schema

NameRequiredDescriptionDefault
updatesYesThe update subscription configuration

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It does not disclose what subscribing entails (e.g., persistent connection, callback mechanism, how to unsubscribe), nor does it indicate side effects or required permissions. The description is insufficient for safe invocation.

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?

The description is a single, concise sentence with no wasted words. However, it lacks structure (e.g., bullet points or sections) and does not front-load critical info. Still, it is appropriately sized for the simple parameter set.

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 (nested object parameter, no output schema, many siblings), the description fails to provide enough context. It does not explain what the return value is, how the subscription works, or how it interacts with other status tools. Incomplete for safe usage.

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% (one parameter fully described). The description adds no new meaning beyond the schema, which already says 'The update subscription configuration'. Baseline is 3, and the description does not exceed it.

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 the verb 'subscribe' and resource 'status updates', indicating a subscription action. However, it is somewhat vague because 'with specific configuration' does not clearly differentiate from other status-related tools (e.g., status_get_*, status_set_*). The lack of a title further reduces clarity.

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 like status_get_* or status_set_*. The description does not mention prerequisites, when not to use, or contrast with siblings. The large number of sibling tools makes this omission particularly problematic.

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