Skip to main content
Glama

docgraph_node

Destructive

Retrieve detailed metadata, structure, and cross-references for a single document or heading. Use the 'section' parameter to read the full content of a specific heading.

Instructions

Get a single document or heading's full details: metadata, structure, and cross-references. Use 'section' to read the full content of a specific heading section from the source file. For multiple documents, use docgraph_explore instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
documentYesDocument name, path, or heading qualified name (e.g. 'docs/guide.md' or 'guide.md#Installation') When copying a path from docgraph_search results, strip the trailing '#heading:line' suffix (and any '[project/]' prefix in workspace mode) to the bare file path before passing it here.
includeBodyNoInclude body excerpt (default true)
sectionNoReturn full content of a specific heading section. Accepts the exact heading text OR the anchor slug shown in search results (e.g. 'Neural Embeddings (agent-driven)' or 'neural-embeddings-agent-driven').
Behavior1/5

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

Description says 'Get' (read-only) but annotations have destructiveHint: true, indicating mutation. This is a severe contradiction; no side effects or behavioral traits disclosed.

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, no wasted words, front-loaded with purpose and usage guidance.

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?

Despite strong parameter details, missing behavioral context (destructive nature due to annotation contradiction) and no output schema described, leaving significant gap for an agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers 100% of parameter descriptions. Description adds value with examples for 'section' (heading text or anchor slug) and cleaning instructions for 'document' (strip suffixes).

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?

Description clearly states verb 'Get' and resource 'single document or heading's full details', and distinguishes from sibling docgraph_explore for multiple documents.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use (single doc/heading) and when not (multiple docs: use docgraph_explore), and explains the 'section' parameter for full content.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Detective-XH/DocGraph'

If you have feedback or need assistance with the MCP directory API, please join our Discord server