Display custom messages on stage screens during presentations using ProPresenter. Control what audiences see in real-time with automated text updates.
Show a message on stage screens
| Name | Required | Description | Default |
|---|---|---|---|
| message | Yes | The message data to display |
Changes observed during successful MCP inspections.
v1.0.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description should disclose side effects (e.g., replaces existing messages?), but it only states the basic action. No details on persistence, visibility duration, or interaction with other stages.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single short sentence is concise, but lacks structured presentation. Could be improved with a brief list of effects.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema and a complex nested parameter, the description is incomplete. Missing return value info, usage examples, and behavioral details.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema describes the 'message' parameter as 'The message data to display', but the description adds no additional meaning. The nested object lacks required fields or structure, leaving ambiguity.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Show a message on stage screens' uses a specific verb ('Show') and resource ('message on stage screens'), clearly distinguishing it from siblings like stage_hide_message and stage_get_message.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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 like messages_create or other stage tools. Missing context on prerequisites or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.