Skip to main content
Glama
Sign In
grimoire

grimoire

by PentHertz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

grimoire_fetch_doc

Fetch the full text of a document indexed from security knowledge sources, using the source and path returned by a search query.

Instructions

Return the full text of one indexed document (markdown, notebook converted to markdown, or extracted PDF text). Use the source+path from a grimoire_search result to read the whole page before answering.

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": {
      "source": "<source>",
      "path": "<path>"
    },
    "name": "grimoire_fetch_doc"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceYessource name from a search result
pathYesrelpath from a search result

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior2/5

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

No annotations are provided, so the description must fully convey behavioral traits. It only describes the return value and usage, omitting side effects, idempotency, authentication needs, rate limits, or any other non-obvious behaviors. This is insufficient for a tool with no annotations.

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 sentences with no wasted words. The first sentence states the purpose, the second gives usage guidance. Front-loaded and efficient.

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?

For a simple two-parameter retrieval tool with no output schema, the description adequately covers input, output, and usage context. Minor omissions like error handling or file size limits are forgivable given the low complexity.

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 coverage is 100% with meaningful property descriptions. The description reinforces that the parameters come from a grimoire_search result but adds little extra semantic value beyond the schema. Baseline 3 is appropriate.

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 returns the full text of one indexed document, specifying document types (markdown, notebook, PDF). It distinguishes itself from sibling tools like grimoire_search by telling the agent to use source+path from a search result, making the purpose and relationship explicit.

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?

The description explicitly says to use source+path from a grimoire_search result, providing clear when-to-use guidance. It does not offer when-not-to-use info or alternatives beyond mentioning the predecessor, but the context is sufficient for typical use.

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