Skip to main content
Glama
lanchuske

Pilot MCP

by lanchuske
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Local

ppt_create

Create a new PowerPoint presentation file on your Mac to start building slides from scratch.

Instructions

Create a new PowerPoint presentation

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • server.js:106-110 (registration)
    The 'ppt_create' tool is registered in the TOOLS array and then registered on the MCP server via server.tool() in a loop. However, the actual handler is just a stub that returns an inspection message.
    for (const [name, desc] of TOOLS) {
  server.tool(name, desc, {}, async () => ({
    content: [{ type: "text", text: "This is an inspection stub. Install Local MCP: npx -y local-mcp@latest setup" }],
  }));
}
  • server.js:70-70 (schema)
    The tool name 'ppt_create' and its description 'Create a new PowerPoint presentation' are defined in the TOOLS array. No input schema is defined (empty object passed to server.tool).
    ["ppt_create", "Create a new PowerPoint presentation"],

Tool Definition Quality

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavior. It only states 'Create a new PowerPoint presentation' without explaining side effects (e.g., does it launch the app, save a file, return a path?). This lack of detail leaves the agent uninformed about what happens during invocation.

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 sentence that is perfectly concise, containing no unnecessary words. It earn its place by directly stating the tool's purpose.

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 tool with no parameters and no output schema, the description is minimally complete. However, it lacks any indication of what the tool returns or the context in which it operates (e.g., does it create a file in a default location?). More detail would improve completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are no parameters, and schema coverage is trivially 100%. The description does not need to add parameter semantics. Baseline for zero parameters is 4, and the description provides no additional parameter info, but this is acceptable.

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 states 'Create a new PowerPoint presentation', specifying the verb (Create) and the resource (PowerPoint presentation). It distinguishes from sibling create tools like 'create_note' or 'excel_create' by naming the specific application.

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 provided on when to use this tool versus alternatives like 'create_note' or 'excel_create'. The agent is left to infer from the name alone, which may be insufficient in ambiguous contexts.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lanchuske/local-mcp-releases'

If you have feedback or need assistance with the MCP directory API, please join our Discord server