Skip to main content
Glama
mcp-library-docs

mcp-library-docs

by roznet

list_libraries

Returns INDEX.md contents from the current project and registered libraries so you can discover existing utilities and avoid reimplementing functionality at task start.

Instructions

Returns INDEX.md contents from the current project and all registered libraries. Call this at the start of a task to discover existing utilities and avoid reimplementing functionality.

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": {
      "cwd": "<cwd>"
    },
    "name": "list_libraries"
  }
}

Input Schema

NameRequiredDescriptionDefault
cwdYesCurrent working directory of the Claude session

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It implies a read operation and specifies scope across the current project and registered libraries, but it does not disclose return format, pagination, permissions, or whether any side effects occur.

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 description is two sentences and front-loads what the tool returns before giving the usage recommendation. Every sentence contributes useful information with no unnecessary wording.

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 read-only tool with one fully documented parameter, the description supplies the core purpose, scope, and usage timing. It could be more complete by mentioning output format or limits, but it is sufficient for an agent to invoke the tool correctly.

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 description coverage is 100%, so the single required cwd parameter is already fully documented in the schema. The description adds no parameter-level meaning beyond what the schema provides, making the baseline 3 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action and resource: it returns INDEX.md contents from the current project and all registered libraries. It is clear what the tool does, though it does not explicitly distinguish itself from siblings such as get_index_status or get_design_doc.

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?

It gives a concrete usage context: call at the start of a task to discover existing utilities and avoid reimplementation. It does not name alternatives or exclusions, but the timing guidance is clear enough for an agent to know when this tool is appropriate.

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