Skip to main content
Glama

Ask a PDF

ask_pdf
Read-onlyIdempotent

Answer a question from the document only, citing pages. Every quote is checked against the page text (verified: false marks one that couldn't be found).

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

Input Schema

NameRequiredDescriptionDefault
fileNoA file the person attached in ChatGPT (filled in by ChatGPT).
file_idNoA FynePDF file_id from upload_file, import_file_from_url or an earlier tool.
file_urlNoA public link to the file.
questionYes
library_file_idNoA file from the person's FynePDF Library (from list_library_files).

Output Schema

NameRequiredDescriptionDefault
foundYes
answerYes
file_idYes
citationsYes
pages_readYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedOutput schema / properties / citations / items / properties / verified / anyOf
      Removed value: -[
      -  {
      -    "type": "boolean"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / citations / items / properties / verified / type
      Added value: +[
      +  "boolean",
      +  "null"
      +]
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Even though the annotations already declare that the tool is read-only, idempotent, and non-destructive, the description adds behavior that those annotations do not cover. It commits to answering solely from the document and to citing pages, and it explains the quote-verification mechanism, including what `verified: false` means. Together, these details set useful expectations about how trustworthy the answer is.

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?

Two short sentences with zero filler. The core capability comes first, and the verification caveat follows. Every clause carries information the agent can use.

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

Completeness4/5

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

Because the tool has an output schema and 80% schema coverage, the description does not need to restate return values or document the parameters, and it appropriately focuses on the grounding and verification behavior. The remaining gap lies in sibling routing among summarize_pdf, search_docs, and this tool.

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 high at 80%, and the schema itself documents file_id, file_url, library_file_id, and the attached-file bundle. The description therefore contributes no additional parameter meaning, which is the baseline 3. It also does not clarify when to prefer file_id versus file_url versus library_file_id.

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 definition uses a concrete verb and resource ("Answer a question from the document"), and the phrase "from the document only" fairly clearly conveys that this is grounded QA with no outside knowledge. However, it never distinguishes this tool from close siblings such as summarize_pdf or search_docs, so an agent still has to infer which of these to use.

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 scope constraint "from the document only" implies that this is a document-grounded question-answering tool. The definition offers no explicit when-to-use versus when-not, and it does not name any alternative. So the usage guidance is only implied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.