Skip to main content
Glama
Sign In
pdf-knowledge-mcp

pdf-knowledge-mcp

by tycket033-tech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ask_pdf_expert

Retrieve relevant local knowledge to answer PDF development questions with source citations.

Instructions

Answer a PDF development question by retrieving relevant local knowledge first and returning an answer with citations.

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": {
      "question": "<question>"
    },
    "name": "ask_pdf_expert"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNoOnly use chunks that contain all of these tags.
limitNoMaximum number of retrieved chunks to use.
questionYesPDF development question to answer with retrieved local knowledge.
maxContextCharsNoMaximum retrieved context characters to include in the answer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations provided; description only says retrieves knowledge and returns answer with citations. Lacks disclosure on side effects, permissions, or dependencies (e.g., prior ingestion).

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?

Single sentence that is clear, front-loaded, and efficient. No waste.

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?

No output schema; description lacks details on answer format, citation structure, or prerequisites. The tool is complex (RAG-based) and needs more context for correct selection and use.

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 100% so baseline 3. Description adds context about retrieval but does not enhance parameter meaning beyond schema.

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?

Clearly states verb 'Answer', resource 'PDF development question', and method 'retrieve local knowledge and return with citations'. Distinguishes from sibling tools like search_knowledge.

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?

Implies usage for PDF development questions but provides no explicit when-to-use or when-not-to-use guidance, nor alternatives. The context from siblings is not referenced.

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