Dockito

Download Slides as a file

export_slides

Read-only

The deck as a file the person can open elsewhere: PDF (a page a slide, text selectable, links that work; hidden slides left out). .pptx isn't ready yet. Answers the file as an embedded resource (base64), often 0.1 to 2 MB; save it, don't read it. Speaker notes go in only when the token can edit. To look at slides, use render.

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": {
      "doc": "<doc>",
      "format": "<format>"
    },
    "name": "export_slides"
  }
}

Input Schema

Name	Required	Description	Default
`doc`	Yes	The doc's link or its code.
`format`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 4, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only declare a safe read (readOnlyHint true, destructiveHint false, openWorldHint false). The description adds substantial context beyond that: the result is returned as a base64 embedded resource of roughly 0.1–2 MB that should be saved rather than read, hidden slides are omitted, links remain functional, and speaker notes are included only when the token has edit rights.

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?

It is front-loaded with the outcome and the format caveat, and nearly every clause carries new information. The telegraphic style is dense but readable; a few fragments could be smoothed without losing content.

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?

With no output schema and only two parameters, the description covers what an agent needs: output format and encoding, size expectations, handling instructions, permission-dependent content, and the sibling alternative. Nothing essential for a correct invocation is missing.

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?

Schema coverage is 50%: 'doc' is documented in the schema, while the 'format' enum values are bare. The description compensates by explaining what the PDF option actually yields (one page per slide, selectable text, working links, hidden slides excluded) and by flagging that pptx is not yet available, which the enum alone would mislead an agent about.

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 concrete verb+resource framing ('The deck as a file the person can open elsewhere') and immediately specifies the PDF output characteristics. It also distinguishes itself from the sibling 'render' tool, which covers viewing slides, so an agent can separate the two without opening either schema.

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 states the selecting condition (the person needs a file to open elsewhere) and explicitly routes the viewing case to 'render'. It also warns that '.pptx isn't ready yet', effectively excluding one enum value. There is no broader when-not guidance, but the routing is clear enough for correct selection.

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

All Dockito tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?