Skip to main content
Glama
ToseaAI

mcp-ToseaAI

Official
by ToseaAI
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

tosea_pdf_to_presentation

Convert PDF files into presentation slides by uploading documents and generating formatted exports in PPTX or PDF formats.

Instructions

Upload local files and generate a final export in one shot.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_pathsYes
instructionNo
output_formatNopptx
render_providerNodefault
render_modelNodeepseek-chat-v3.1
slide_domainNogeneral
page_count_rangeNo8-12
template_nameNobeamer_classic
slide_modeNohtml

Implementation Reference

  • src/tools.ts:329-355 (handler)
    The handler function for the tosea_pdf_to_presentation tool, which calls the client's pdfToPresentation method.
    async ({
  file_paths,
  instruction,
  output_format,
  render_provider,
  render_model,
  slide_domain,
  page_count_range,
  template_name,
  slide_mode
}) => {
  try {
    return asToolResult(
      await client.pdfToPresentation({
        filePaths: file_paths,
        instruction,
        outputFormat: output_format,
        renderProvider: render_provider,
        renderModel: render_model,
        slideDomain: slide_domain,
        pageCountRange: page_count_range,
        templateName: template_name,
        slideMode: slide_mode
      })
    );
  } catch (error) {
    throw wrapToolError(error);
  • src/tools.ts:315-328 (registration)
    The registration of the tosea_pdf_to_presentation tool, including its parameter schema definition.
    server.tool(
  "tosea_pdf_to_presentation",
  "Upload local files and generate a final export in one shot.",
  {
    file_paths: z.array(z.string().min(1)).min(1).max(10),
    instruction: z.string().default(""),
    output_format: z.enum(["pdf", "pptx", "pptx_image"]).default("pptx"),
    render_provider: z.string().default("default"),
    render_model: z.string().default("deepseek-chat-v3.1"),
    slide_domain: z.string().default("general"),
    page_count_range: pageCountRangeSchema.default("8-12"),
    template_name: z.string().default("beamer_classic"),
    slide_mode: z.enum(["html", "image"]).default("html")
  },

Tool Definition Quality

C2.4/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions uploading files and generating an export 'in one shot', suggesting a batch operation, but doesn't cover critical behaviors like authentication needs, rate limits, file size constraints, error handling, or what the export output entails (e.g., file format, location). This leaves significant gaps for an agent to understand how to invoke it safely and effectively.

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, efficient sentence that gets straight to the point without fluff. It's front-loaded with the core action, though it could be more structured by hinting at key parameters. There's no wasted verbiage, earning it a high score for conciseness.

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?

Given the complexity (9 parameters, 0% schema coverage, no annotations, no output schema), the description is incomplete. It doesn't address parameter meanings, behavioral traits, or output details, leaving the agent with insufficient context to use the tool effectively. The description alone fails to bridge the gaps in structured data.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate, but it adds no meaning beyond the schema. It doesn't explain what parameters like 'instruction', 'render_provider', 'slide_domain', or 'page_count_range' do, or how they affect the presentation generation. With 9 parameters (3 with enums) and no output schema, this lack of semantic context is a major gap.

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

Purpose3/5

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

The description states the tool 'upload[s] local files and generate[s] a final export' which gives a basic purpose, but it's vague about what kind of export (presentation from PDFs) and doesn't differentiate from siblings like 'tosea_export_presentation' or 'tosea_render_slides'. It mentions 'in one shot' implying a batch process, but lacks specificity about the transformation from PDF to presentation.

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 on when to use this tool versus alternatives like 'tosea_export_presentation' or 'tosea_render_slides'. The description implies a full workflow from upload to export, but doesn't specify prerequisites, context, or exclusions. Usage is implied by the action described, but no explicit guidelines are provided.

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/ToseaAI/mcp-ToseaAI'

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