io.github.Headdao/slidemaster-mcp

upload_init

Initialize an upload session for an existing PPTX or PDF presentation to receive a pre-signed upload URL and project ID for the file transfer.

Instructions

Initialize a file upload session for an existing presentation file (PPTX/PDF). Returns a pre-signed upload URL and project_id.

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": {
      "title": "<title>",
      "filename": "<filename>"
    },
    "name": "upload_init"
  }
}

Input Schema

Name	Required	Description	Default
`title`	Yes	Title for the uploaded presentation
`filename`	Yes	Original filename including extension, e.g. 'deck.pptx'

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.2Sep 6, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description must carry the full behavioral disclosure burden. It mentions the return values but omits important behavior: whether this creates state, whether the URL expires, whether the actual file bytes are sent later, and whether upload_complete must be called afterward.

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 sentence with no filler and front-loads the core action. The phrase 'existing presentation file' could be clearer, but overall it is appropriately concise.

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?

The description does not explain the overall upload workflow or that a follow-up call to upload_complete is likely required. Since there is no output schema, the agent cannot infer how to proceed after receiving the pre-signed URL.

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%, so the description does not need to add parameter details. It does add the constraint that files are PPTX/PDF, but the baseline of 3 is appropriate since the schema already documents title and filename clearly.

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

Purpose4/5

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

The description clearly names the action ('Initialize a file upload session') and the resource ('presentation file (PPTX/PDF)'), and states the key result (pre-signed URL and project_id). It is distinguishable from the sibling upload_complete because 'initialize' and 'complete' indicate different phases.

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 given about when to use this tool versus upload_complete or other siblings. The description does not mention that this is the first step in a multi-step upload flow, nor does it state any prerequisites or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.