io.github.Headdao/slidemaster-mcp

list_slides

Retrieve all slides for a project by ID, showing titles, scripts, and render status to track presentation progress.

Instructions

List all slides belonging to a specific project, including their titles, scripts, and render status.

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": {
      "project_id": "<project_id>"
    },
    "name": "list_slides"
  }
}

Input Schema

Name	Required	Description	Default
`project_id`	Yes	Project ID to list slides for

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.2Sep 6, 2026

TDQS

A3.8/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 of behavioral disclosure. It usefully states that the result includes titles, scripts, and render status, but it does not explicitly confirm the operation is read-only or describe ordering, pagination, or empty-result behavior.

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, action-first sentence with no filler. It efficiently conveys the resource, scope, and primary output fields in one line.

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

Completeness4/5

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

For a simple one-parameter list operation with no output schema, the description provides adequate context by naming what the response contains. Minor details such as result ordering, sorting, or behavior for projects with no slides are not specified, but they are not critical for selecting or invoking this tool.

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%, and the only parameter, project_id, already has a clear schema description. The tool description adds only the generic phrase 'a specific project' and no extra detail about where the ID comes from or what values are valid, landing at the baseline.

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 opens with a specific action and resource: 'List all slides belonging to a specific project.' It also names the key output fields (titles, scripts, render status), making the tool's purpose immediately clear and distinguishable from sibling tools like list_projects or get_project.

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

Usage Guidelines3/5

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

The description clearly implies its use case: call this tool when you need all slides for a known project_id. However, it does not explicitly contrast it with alternatives such as get_project or list_projects, nor does it state when not to use it, so routing between siblings is left to inference.

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