Skip to main content
Glama

pdf_rag_chunks

Extract semantic RAG chunks from PDF files into JSON arrays. Use it to prepare document content for retrieval-augmented generation pipelines.

Instructions

Extract semantic RAG chunks from PDF. [Input: PDF (.pdf) | Output: JSON array]

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

Input Schema

NameRequiredDescriptionDefault
inputYes
outputNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/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. It only states input format and that the result is a JSON array; it says nothing about chunk size, overlap, semantic model behavior, handling of scanned PDFs, or whether any file is written to disk (relevant since there is a string "output" parameter).

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 compact clauses, front-loaded with the action and followed by a bracketed input/output summary. Nothing is padded, though the brevity comes at the cost of missing detail rather than being a model of efficiency.

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?

With no annotations, no output schema, and an undocumented "output" parameter, the description is too thin for a tool whose behavior (chunk sizing, semantic boundaries, file output) materially affects results. An agent could invoke it but cannot predict what it will get.

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

Parameters2/5

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

Schema description coverage is 0% for two parameters, so the description must compensate and does not. It hints that input is a .pdf path, but the "output" string parameter is entirely unexplained and is even potentially misleading given the description claims the output is a JSON array rather than a file.

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 names a specific verb and resource ("Extract semantic RAG chunks from PDF"), so the agent knows it produces retrieval-ready chunks rather than plain text. However, it never distinguishes itself from the sibling pdf_chunk or pdf_extract_text, leaving ambiguity about which chunking tool to pick.

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 at all: no statement about when semantic RAG chunking is preferable to plain chunking or text extraction, and no prerequisites such as whether the PDF must be text-based or OCR'd. The agent must guess from the name alone.

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