Skip to main content
Glama
renvk

pdf-search-mcp

by renvk

search

Perform full-text search across PDF documents with support for phrases, operators, and automatic query relaxation. Returns results with file, page, and snippet.

Instructions

Search indexed PDFs using FTS5 full-text search.

Supports FTS5 syntax: phrases ("exact phrase"), AND (implicit), OR, NOT, prefix (term*), NEAR(term1 term2, 10), parentheses.

Terms with special characters (dots, hyphens, colons, slashes, ...) are auto-quoted — FTS5 treats them as token separators. You can also quote them yourself: "13445-3", "v2.1".

German ß↔ss / ä↔ae / ö↔oe / ü↔ue variants are expanded automatically.

When no results match all terms (implicit AND), the query is automatically relaxed: first by dropping the term least represented in the corpus, then by OR-ing all terms. A note at the top explains what was searched. Structured queries (explicit operators, NEAR, parentheses) are never relaxed.

Args: query: Search query string. limit: Maximum number of results (default 10, range 1-50).

Returns: Formatted search results with file, subfolder, page, and snippet.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
limitNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Without annotations, the description fully discloses behavioral traits: auto-quoting special characters, German character expansion, automatic query relaxation, and structured queries not being relaxed. It also mentions a note explaining relaxed searches.

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?

The description is well-structured with front-loaded purpose and detailed syntax info. It is reasonably concise, though some sections (like auto-relaxation) could be slightly more condensed without losing clarity.

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?

Given the complexity of FTS5 search with special syntax and auto-relaxation, the description covers all necessary aspects. Output schema exists (described in return format), and no additional info is needed for the tool's usage.

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 0%, so the description adds meaning for both parameters: 'query' is the search string, 'limit' is max results with default 10 and range 1-50. However, it does not elaborate on edge cases or behavior beyond basic details.

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 clearly states the tool's purpose: 'Search indexed PDFs using FTS5 full-text search.' It uses a specific verb (search) and resource (indexed PDFs), and is distinct from sibling tools like read_page, read_page_image, and stats.

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 usage (to search text in PDFs) but does not explicitly state when to use this tool versus alternatives or provide exclusions. Sibling differentiation is implicit but no direct guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/renvk/pdf-search-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server