Skip to main content
Glama

local-mcp

by com.local-mcp
OverviewDiscussionsAdmin

PDF Read

pdf_read
Read-only

Reads and extracts text from a PDF document (.pdf file).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesAbsolute path to the PDF file
max_pagesNoMax pages to extract (default: all)
force_downloadNoIf the file is stored in the cloud and evicted from this Mac (dataless), request the download and wait for it instead of failing. Off by default: a download can take minutes and use metered data, so it is the caller's decision.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesExtracted text content
charsYesNumber of characters in the extracted text
pagesNoTotal number of pages in the PDF

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / force_download
      Added value: +{
+  "description": "If the file is stored in the cloud and evicted from this Mac (dataless), request the download and wait for it instead of failing. Off by default: a download can take minutes and use metered data, so it is the caller's decision.",
+  "type": "boolean"
+}
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, providing safety information. The description adds minimal behavioral detail beyond the core action, such as potential side effects or performance considerations. The parameter description for force_download does add context about cloud eviction, but the main description itself is sparse.

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?

The description is a single, succinct sentence that conveys the essential purpose. It is front-loaded with the verb and resource, with no unnecessary words or redundant detail.

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

Completeness4/5

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

The tool is simple and the output schema is present, so the description need not explain return values. The parameter descriptions and annotations cover the key operational context. It could mention typical use cases or limitations, but nothing critical is missing for a basic read operation.

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

Parameters4/5

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

All parameters have descriptions covering 100% of the schema. The force_download parameter description goes beyond the schema by explaining the default behavior and rationale ('Off by default: a download can take minutes and use metered data'), which adds meaningful semantic detail. path and max_pages descriptions are clear though somewhat generic, leading to a score just above baseline.

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

Purpose5/5

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

The description 'Reads and extracts text from a PDF document' clearly states the action (read/extract) and the resource (PDF file). It is specific enough to distinguish from sibling file-read tools like file_read or gdrive_read_file, which handle other file types.

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?

The description implies use for PDF files but does not explicitly state when to prefer this over alternatives like file_read or onedrive_read_file. The name and context make the choice reasonably clear, but there is no direct guidance on alternatives.

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

All local-mcp toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources