Skip to main content
Glama

pdf_classify_type

Classify a PDF's document type using heuristics to determine what kind of file you are working with before processing.

Instructions

Classifies the PDF document type based on heuristics.

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": {
      "input": "<input>"
    },
    "name": "pdf_classify_type"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYesThe input PDF file path.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description carries the full burden, and it only hints at behavior via "based on heuristics" — useful signal that results are approximate, but there is no disclosure of what categories are returned, confidence, or failure behavior on malformed/non-PDF input. No output schema exists, so the return value is completely undocumented.

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?

One efficient sentence with no wasted wording and the purpose front-loaded, though brevity here shades into under-specification rather than crispness.

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?

For a classifier with no annotations and no output schema, the description needs to state the label set and return shape; it states neither. An agent can invoke it but cannot anticipate or interpret the result.

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

Parameters3/5

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

There is a single parameter documented at 100% coverage in the schema ("The input PDF file path"), so the schema does the work. The description adds nothing about the parameter beyond what is already stated, which is the expected baseline for a fully documented one-param tool.

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?

"Classifies the PDF document type" names a verb and resource, but leaves the classification taxonomy undefined — an agent cannot tell whether this yields scanned-vs-digital, invoice-vs-receipt, or form-vs-text categories. Nothing distinguishes it from the many pdf_* siblings, which are all converters/extractors rather than classifiers.

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?

There is no guidance on when to call this rather than, say, pdf_extract_text or pdf_compare, nor any prerequisite such as a valid readable PDF path. Usage must be inferred entirely from the tool name.

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