Skip to main content
Glama

tosea_parse_pdf

Parse PDF documents to extract content for presentation creation, generating a presentation ID and job payload for slide development.

Instructions

Upload local files and run the parse-only stage. Returns a presentation_id and job payload.

Input Schema

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

Implementation Reference

  • Registration and handler for tosea_parse_pdf tool, which calls client.pdfParse.
    server.tool(
      "tosea_parse_pdf",
      "Upload local files and run the parse-only stage. Returns a presentation_id and job payload.",
      {
        file_paths: z.array(z.string().min(1)).min(1).max(10),
        instruction: z.string().default(""),
        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")
      },
      async ({
        file_paths,
        instruction,
        render_provider,
        render_model,
        slide_domain,
        page_count_range,
        template_name,
        slide_mode
      }) => {
        try {
          return asToolResult(
            await client.pdfParse({
              filePaths: file_paths,
              instruction,
              renderProvider: render_provider,
              renderModel: render_model,
              slideDomain: slide_domain,
              pageCountRange: page_count_range,
              templateName: template_name,
              slideMode: slide_mode
            })
          );
        } catch (error) {
          throw wrapToolError(error);
        }
      }
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 returning a presentation_id and job payload, but fails to detail critical aspects like authentication needs, rate limits, error handling, or what the 'parse-only stage' involves (e.g., text extraction, structure analysis). This leaves significant gaps in understanding the tool's behavior and constraints.

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 concise and front-loaded, stating the core action and return value in one sentence. There's no wasted text, and it efficiently communicates the basic purpose without unnecessary elaboration, though it could benefit from more detail given the complexity.

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 tool's complexity (8 parameters, no annotations, no output schema), the description is incomplete. It doesn't explain the parsing process, output format, error conditions, or how the returned presentation_id and job payload are used. Without this context, users may struggle to integrate the tool effectively into workflows.

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 by explaining parameters, but it adds no meaning beyond the schema. It doesn't clarify what 'instruction', 'render_provider', or other parameters do, nor does it provide context for enums like 'slide_mode'. With 8 parameters and no schema descriptions, this lack of semantic information 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 action ('Upload local files and run the parse-only stage') and the resource (PDF files), but it's vague about what 'parse-only stage' entails. It doesn't clearly distinguish this tool from sibling tools like 'tosea_pdf_to_presentation' or 'tosea_render_slides', leaving ambiguity about the specific parsing function versus full presentation generation.

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. For example, it doesn't explain if this is a preliminary step before 'tosea_pdf_to_presentation' or how it differs from 'tosea_render_slides'. The description lacks context about prerequisites, sequencing, or exclusions, offering minimal usage direction.

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