Skip to main content
Glama
Sign In
PresentationMcpServer

PresentationMcpServer

by CompSciGuyIT
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get deck

get_deck

Retrieve a complete deck manifest with scope-ledger summary and bundle file paths for a given deck ID.

Instructions

Full manifest + scope-ledger summary + bundle file paths for one deck.

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": {
      "deckId": "<deckId>"
    },
    "name": "get_deck"
  }
}

Input Schema

NameRequiredDescriptionDefault
deckIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior2/5

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

No annotations exist, and the description doesn't disclose whether this is read-only, error behavior for missing IDs, or required permissions. It only lists return content.

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?

One concise sentence, no fluff, front-loaded with the action and key result.

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?

For a simple getter with no output schema, it lists return components but omits error handling and read-only guarantees; sufficient but not fully complete.

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 schema has zero coverage for deckId; the description adds that it identifies one deck but doesn't clarify ID format or origin, leaving the parameter's semantics partially inferred.

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 specifies a clear retrieval action for one deck and lists the exact returned components (manifest, scope-ledger summary, bundle file paths), distinguishing it from list_decks and render_deck.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It implies usage when full details for a single deck are needed, but it doesn't explicitly state common alternatives or when not to use it. The context is clear enough for a basic getter.

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