Skip to main content
Glama
dis70rt

closed-book-mcp

by dis70rt

closed_book_search

Search authoritative study materials in PDFs using hybrid semantic and keyword matching to retrieve relevant content for answering closed-book questions.

Instructions

Search the authoritative study materials using Hybrid Search. The returned content comes directly from the user's PDFs. This is the primary knowledge retrieval tool for closed-book questions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
top_kNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations provided, the description carries full burden. It discloses that it performs a search over user PDFs and returns content directly from them, which is the core behavior. It does not mention any side effects, permissions, or edge cases, but for a search tool this is adequate.

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 concise sentences with the main action front-loaded. No fluff; each sentence earns its place.

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?

Given the tool's simplicity (2 params, output schema exists), the description covers the essential purpose and source. It lacks detail on result format or pagination, but the output schema likely covers that. It adequately enables an agent to call it correctly.

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%, and the description does not explain either parameter. The names 'query' and 'top_k' are self-explanatory, but the description adds no additional semantics beyond the schema, failing to compensate for the low coverage.

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?

States a specific verb ('Search'), resource ('authoritative study materials'), and method ('Hybrid Search'), and clarifies the source (user's PDFs). Distinguishes from siblings by positioning itself as the primary retrieval tool for closed-book questions.

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?

Explicitly identifies its role as the primary knowledge retrieval tool for closed-book questions, giving clear context for when to use it. Does not explicitly contrast with siblings, but the context is clear enough for selection.

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