Skip to main content
Glama
Sign In
propresenter-mcp

propresenter-mcp

by Marc416
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_presentation

Retrieve detailed information about a specific ProPresenter presentation using its unique identifier (UUID).

Instructions

Get details of a specific presentation by UUID

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": {
      "presentationUuid": "<presentationUuid>"
    },
    "name": "get_presentation"
  }
}

Input Schema

NameRequiredDescriptionDefault
presentationUuidYesThe UUID of the presentation

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It indicates a read-only operation ('Get details') with no side effects, which is adequate but not explicit about behavior like permissions, rate limits, or return format. The lack of detail beyond the name and schema limits transparency.

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 concise sentence of 9 words that directly states the tool's purpose with no redundant or unnecessary information. It is well-structured and front-loaded.

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

Completeness3/5

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

Given the absence of an output schema, the description should ideally hint at the type of details returned (e.g., title, slides, properties). It is minimally complete but leaves the agent uncertain about the value of the response. Sibling tools provide enough context, but the description itself is sparse.

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 description coverage is 100% (the sole parameter 'presentationUuid' is described in the schema). The description adds 'by UUID,' which is already implied by the schema. No additional meaning is provided beyond the schema, so a baseline score of 3 is appropriate.

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 specifies the verb ('Get'), the resource ('details of a specific presentation'), and the unique identifier method ('by UUID'). It distinguishes itself from sibling tools like 'get_active_presentation' or 'get_focused_presentation' by emphasizing the specific UUID parameter.

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?

The description provides no guidance on when to use this tool instead of alternatives (e.g., get_active_presentation, get_focused_presentation, get_presentation_thumbnail). It only states the basic function, leaving the agent to infer appropriateness from context.

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