Skip to main content
Glama
Sign In
pdf-context

pdf-context

by mematcha
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_structure_tool

Get the complete outline and section hierarchy of an indexed PDF, including node IDs for precise navigation.

Instructions

Get the full table-of-contents / structure tree for an indexed PDF.

Use when the user needs the complete outline, section hierarchy, or node IDs for navigation—not just top-level chapters.

Do not use for repo directory trees or documents not in list_documents.

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": {
      "document": "<document>"
    },
    "name": "list_structure_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
documentYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.4/5.0
Behavior4/5

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

No annotations provided, so the description carries full burden. It describes the tool as retrieving structure for indexed PDFs and includes node IDs, indicating a read operation. It does not explicitly state that it is non-destructive or require authorization, but the use context is clear.

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 sentences, front-loaded with the core purpose, followed by usage guidelines and exclusions. No wasted words.

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 (one parameter) and the presence of an output schema, the description adequately covers what the tool does, when to use it, and constraints. Could provide slightly more detail on the parameter's nature.

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 has 0% description coverage; the description indirectly explains the document parameter by referencing 'indexed PDF' and 'documents not in list_documents'. However, it does not specify the parameter's format or source, leaving some ambiguity.

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 that the tool retrieves the full table-of-contents/structure tree for an indexed PDF, specifying it provides node IDs for navigation. It distinguishes from siblings by noting it's not just top-level chapters.

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 states when to use (complete outline, section hierarchy, node IDs) and when not to use (repo directory trees, documents not in list_documents). Provides clear guidance on appropriate use cases.

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