Skip to main content
Glama
Local Development MCP Server

Local Development MCP Server

by lreb

read-pdf

Extract and read text content from a PDF file, optionally limiting extraction to a start and end page for focused document review.

Instructions

Extract and read text content from a PDF file

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": {
      "path": "<path>"
    },
    "name": "read-pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesAbsolute or relative path to the PDF file
pageEndNoOptional: End page (inclusive)
pageStartNoOptional: Start page (1-indexed)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it discloses almost nothing beyond the basic operation. It does not state whether output is plain text or includes page markers, whether OCR happens on scanned documents, how large files are handled, or what errors occur for missing/encrypted files.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single, front-loaded sentence with zero preamble or hedging. Nothing in it is redundant, and the core operation is the first thing the reader sees.

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?

There is no output schema and no annotations, so the description is the only place an agent could learn what the tool returns, and it says nothing about return shape or how pageStart/pageEnd affect the output. For a low-complexity tool the parameter documentation in the schema helps, but the missing behavioral and output context leaves the definition under-specified.

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?

Schema description coverage is 100%, with path, pageStart, and pageEnd all documented including 1-indexed and inclusive semantics, so the schema already does the explanatory work. The description adds no meaning beyond the schema, which is the baseline-3 case rather than a deficiency.

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 states a specific verb pair (extract and read) and a specific resource (text content from a PDF file), so an agent immediately knows the operation. It does not name or contrast with the obvious sibling read-file, so the PDF-specific distinction is left implicit rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the agent can infer 'use this for PDFs, use read-file for other files,' but the description never says so explicitly. There is no guidance on exclusions, such as scanned/image-only PDFs that yield no text, encrypted PDFs, or non-PDF inputs, which are realistic failure modes for this tool.

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