Skip to main content
Glama
Sign In
stayput-mcp

stayput-mcp

by keenanlk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

PDF info

pdf_info
Read-only

Read a PDF locally to report page count, page sizes, title, and encryption status before splitting, extracting, or rotating pages. Fails clearly if the file is not a PDF or needs a password.

Instructions

Read a PDF on this machine and report its page count, page sizes, title and whether it was encrypted. Read-only: nothing is written. Use before split_pdf, extract_pdf_pages or rotate_pdf to learn the page count. Fails with a readable error if the file is not a PDF or needs a password.

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": "pdf_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesPath to the PDF.
passwordNoPassword for a PDF that asks for one when opened. Used only on this machine.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so 'nothing is written' is largely redundant. The description does add genuine value beyond the annotations: the readable-error failure mode for non-PDFs/password-locked files and the assurance that a supplied password is used only locally.

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?

Three tight sentences with the primary action and return fields front-loaded, followed by usage routing and failure behavior. No filler or repetition.

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

Completeness5/5

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

With no output schema available, the description compensates by listing the returned fields (page count, page sizes, title, encryption) and the error behavior. It covers everything an agent needs to select and invoke the tool correctly.

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 coverage is 100%, with both parameters documented in the schema itself. The description only implies the password parameter's purpose ('needs a password') without adding format, source, or handling detail beyond what the schema states, so the baseline of 3 applies.

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 states a specific verb (read/report) and resource (PDF) and enumerates exactly what is reported: page count, page sizes, title, encryption status. This clearly separates it from mutation siblings like split_pdf and rotate_pdf.

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

Usage Guidelines5/5

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

It explicitly tells the agent when to use it ('before split_pdf, extract_pdf_pages or rotate_pdf to learn the page count') and names the concrete downstream tools that depend on this information. The failure conditions (non-PDF, password-protected) further define its operating envelope.

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

Deploy Server

Other Tools