Skip to main content
Glama

ask-document

Answers questions about an indexed course document to help PMP candidates clarify concepts, processes, and approach differences; build the index first with extract-document-index.

Instructions

Answers any question about your course document using GPT-4o. Perfect for PMP exam preparation: ask about concepts, processes, differences between approaches, etc. Requires the index to be built first with extract-document-index.

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

Input Schema

NameRequiredDescriptionDefault
chapterNoRestrict the search to a specific chapter (optional)
documentNoDocument name to search in (use list-documents to see available). Auto-detected if only one document is indexed.
pmpFocusNoIf true, frames the answer in PMP exam context (default: true)
questionYesYour question about the document (in French or English)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden; it discloses the GPT-4o backing and the index prerequisite, which are useful. However, it does not state that the operation is read-only, what happens when the index is absent, or whether answers are grounded or cited. Those omissions matter for a query tool with no annotation safety profile.

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?

Three compact sentences, front-loaded with purpose, followed by use case and prerequisite. Every sentence adds useful context and there is no filler.

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

Completeness3/5

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

The description is adequate for a Q&A tool: it gives purpose, a use case, and the index prerequisite. But with no output schema and no annotations, it should also describe the return format (plain answer, citations, etc.) and behavior when the index is missing. These are clear gaps.

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 the four parameters are already documented in the schema. The description adds no parameter-level meaning (for example, how pmpFocus changes output or how chapter scoping works) beyond the schema. Baseline 3 is correct.

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 action (answer questions), resource (course document), and implementation (GPT-4o), and it scopes the content to PMP exam topics. It does not explicitly contrast with siblings like generate-quiz or generate-document-pdf, so differentiation is only partial.

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?

It states a concrete use case (PMP exam preparation) and a hard prerequisite: the index must be built first with extract-document-index. It does not name alternative tools or say when not to use it, keeping it just short of full routing guidance.

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