Skip to main content
Glama
Sign In

Kyle Romero (kgromero.com)

by io.github.romero927
OverviewDiscussionsAdmin

get_document

Read-onlyIdempotent

Read a document from kgromero.com: PDFs as text, diagrams and photos as images.

Many PDFs are slide decks or scans; the text result lists pages that are mostly
visual so you can call again with as_images=true to see them. Results for files on
the site end with a link to the original file.

Args:
    document: Name, part of a name, filename, or URL from list_documents
        (e.g. "Electron Architecture", "Transcript", "RedditListener").
    pages: PDF pages to return, e.g. "3", "1-5", or "2,4,7-9". Defaults to all
        pages for text (up to a length limit).
    as_images: Return PDF pages as images instead of text (up to 5 pages per call).

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": {
      "document": "<document>"
    },
    "name": "get_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
pagesNo
documentYes
as_imagesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/closed-world, and the description still adds substantive behavior: text output is capped by a length limit, image mode is capped at 5 pages per call, and results for site-hosted files end with a link to the original. Those are operational details an agent cannot get from the schema or annotations.

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?

Purpose and the visual-page hint are front-loaded, then a compact Args block covers the three parameters with no repeated sentences and no filler. Every line either routes the agent or specifies a format.

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?

There is no output schema, and the description compensates by describing the result shape (page listing, image mode, trailing original-file link) along with the truncation caveat. For a 3-parameter read tool this leaves nothing an agent needs missing.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must carry the parameter burden and it does: document accepts a name, partial name, filename, or URL with three concrete examples; pages accepts "3", "1-5", "2,4,7-9" and defaults to all; as_images is explained along with its 5-page cap.

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?

States a specific verb and resource ("Read a document from kgromero.com") plus the two return modalities (text for PDFs, images for diagrams/photos). It also points at list_documents as the source of valid document identifiers, so an agent can separate retrieval from enumeration without opening a schema.

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

Usage Guidelines4/5

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

Gives a concrete conditional workflow: if the text result shows many visual pages, call again with as_images=true. It also tells the agent where names come from (list_documents). It stops short of stating when NOT to use it (e.g., vs. search or list_documents) but the retrieval context is clear.

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

All Kyle Romero (kgromero.com) 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