KitchenSink4PPT

Overview Schema Source Related Servers Score Discussions Admin

diagnose

Read-only

Check the environment and, optionally, one file: reports engine availability, sandbox state, lock status, and slide count without modifying anything. Output is paste-safe for bug reports.

Instructions

Self-check for this environment and, optionally, one file. Reports export engine availability (PowerPoint COM vs LibreOffice), sandbox state, KS4P mode/policy env, and the current pack surface with token costs. With file_path: existence, size, PowerPoint lock state, whether the package opens, and slide count, WITHOUT mutating anything. Output is PASTE-SAFE by default: no absolute paths, so it can go straight into a bug report; verbose=True adds the sandbox roots, engine locations, and full file path for local troubleshooting. Run it first when any tool refuses unexpectedly or an export engine seems missing. Reports the update-check state; the only place the check runs. The validate tool (assembly-export pack) does the real opens-clean check in PowerPoint.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`verbose`	No
`file_path`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.2.1Sep 9, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
Changed1 schema field changedv1.1.3Sep 8, 2026
- addedInput schema / properties / verbose
```
Added value: +{
+  "default": false,
+  "type": "boolean"
+}
```
First observedv1.0.0Aug 31, 2026

TDQS

A5/5.0

Behavior5/5

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

ReadOnlyHint already marks it read-only, and the description reinforces this with 'WITHOUT mutating anything.' It also adds valuable behavioral context: output is PASTE-SAFE by default, verbose=True exposes paths, and it is the only place the update-check runs.

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 dense but every sentence contributes: what it checks, optional file behavior, output safety, when to run it, and the boundary with validate. The key purpose is front-loaded in the first sentence.

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

Completeness5/5

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

Given the output schema exists, the description need not enumerate return fields. It covers the diagnostic scope, safety profile, parameter effects, invocation timing, and the sibling tool boundary, making it complete for an agent deciding whether and how to call diagnose.

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

Parameters5/5

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

With 0% schema description coverage, the description carries full responsibility for explaining parameters. It clearly explains file_path enables file-level checks, and verbose=True adds sandbox roots, engine locations, and the full file path, which goes beyond the schema's bare types.

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 states a specific verb ('Self-check') and resource ('this environment and, optionally, one file'), and enumerates exactly what it reports. It also differentiates itself from the validate tool, so an agent can distinguish diagnose from a real PPT opens-clean check.

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

Usage Guidelines5/5

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

The description explicitly says 'Run it first when any tool refuses unexpectedly or an export engine seems missing,' and tells the agent that validate is the tool for the actual opens-clean check in PowerPoint. This gives clear when-to-use and when-not-to-use guidance.

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