Skip to main content
Glama

pdf_info

Extract basic PDF information, including page count, from a local file and output it as a JSON object.

Instructions

Get basic PDF information like page_count. [Input: PDF (.pdf) | Output: JSON object]

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_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYesThe path to the input PDF file.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations and no output schema, the description carries the full disclosure burden, yet it only says the result is a "JSON object" with "basic PDF information like page_count". It does not enumerate the returned fields, state behavior on encrypted or malformed PDFs, or confirm the operation is read-only.

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?

Two short, front-loaded segments with the purpose first and the I/O contract second; no wasted prose. The bracketed format notation is compact rather than verbose.

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

Completeness3/5

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

For a one-parameter inspection tool this is close to adequate, and the input side is fully covered. The main gap is the undefined return payload, which matters because no output schema exists to fill that hole.

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?

The single input parameter is fully documented in the schema at 100% coverage, so the baseline is 3. The description's only added detail is the expected file format (PDF/.pdf), which is marginal extra meaning.

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

Purpose4/5

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

The description gives a specific verb and resource ("Get basic PDF information") plus a concrete example field (page_count), which separates it from siblings that transform or extract content. It stops short of naming an explicit contrasting sibling such as pdf_extract_text or pdf_classify_type, so an agent must infer the boundary.

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 when-to-use guidance, no prerequisite or exclusion notes, and no pointer to alternatives. An agent can guess this is a cheap metadata probe, but nothing in the text states that.

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