Skip to main content
Glama
Local Development MCP Server

Local Development MCP Server

by lreb

list-indexes

List all available document indexes to identify which indexed documents can be searched or managed.

Instructions

List all available document indexes

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": "list-indexes"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. 'List all available' implies a read-only, non-destructive enumeration, which is useful implicit context, but it says nothing about whether results are paginated, whether index names/ids/content are returned, or what happens if no indexes exist.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with the verb front-loaded and no redundant wording. It is appropriately sized for a zero-parameter tool, though the brevity leaves no room for the operational context noted above.

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

Completeness3/5

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

For a simple zero-param listing tool with no output schema, the definition covers the bare minimum: what it returns at a high level and that it is unfiltered. It is missing what an 'index' identifier looks like and any relationship to index-documents, which an agent would need to chain calls correctly.

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?

The tool takes zero parameters, and the description correctly indicates a global listing with no filtering arguments, so there is no schema meaning left to compensate for.

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?

States a specific verb ('List') and resource ('document indexes') with a scope qualifier ('all available'). This is clear enough to distinguish it from mutation-oriented siblings like index-documents, but the description never explicitly says how it differs from that sibling.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance. An agent must guess whether to call this before 'index-documents' (to create an index) or 'search-documents' (to query one), and the description provides no routing to those alternatives.

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