Skip to main content
Glama
Sign In
lichtblick-docs-mcp

lichtblick-docs-mcp

Official
by lichtblick-suite
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List Lichtblick documentation pages

docs_list
Read-only

List all Lichtblick documentation and guide pages with paths and summaries to discover available content when search is insufficient; fetch pages for details.

Instructions

Lists every page of the official Lichtblick documentation and guides with its path and summary. Use it to discover what is documented when docs_search is not enough; then read a page with docs_fetch.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "docs_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectionNoOnly list pages of this section: "Documentation" or "Guides".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.0
    • changedInput schema / properties / section / description
      Previous value: -"Only list pages of this section, e.g. \"Documentation\" or \"Guides\"."New value: +"Only list pages of this section: \"Documentation\" or \"Guides\"."
  2. First observedv0.0.0

TDQS

A4.5/5.0
Behavior4/5

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

The description adds valuable behavioral context by specifying that the tool returns 'path and summary' for every page, even though no output schema is provided. This complements the readOnlyHint annotation well.

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?

The definition is highly efficient, using only two sentences that each carry distinct, non-redundant information (what it does, and why/how to use it). It is front-loaded and easy to parse.

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

Completeness5/5

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

Given that it is a list tool and no complex output schema exists, the definition is highly complete. It tells the agent what data to expect (path/summary) and how to integrate it into a larger plan involving sibling tools.

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?

With 100% schema coverage, the description primarily serves to reinforce the parameter constraints (Documentation/Guides) already present in the input schema. It does not add deep meaning or complex semantics beyond the structured fields.

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 uses strong active verbs to clarify that it 'lists' pages and specifies exactly what data is returned: path and summary. It clearly defines the resource (Lichtblick documentation and guides).

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?

The definition provides explicit guidance on when to use this tool versus the alternative: use docs_list 'when docs_search is not enough'. It also clarifies the next step in the workflow, which is 'read a page with docs_fetch.'

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