Skip to main content
Glama
manticoresoftware

Manticore Search MCP

Official

list_documentation

Filter and retrieve Manticore Search documentation files using regex patterns to efficiently find multiple topics in a single call.

Instructions

List available documentation files from Manticore Search manual.

IMPORTANT: Make ONE call with regex OR patterns to find multiple topics at once. DO NOT make multiple calls - use pipe (|) to combine patterns.

The file list is cached, so filtering is instant and local.

Args: search: Regex pattern to filter files (case-insensitive). Use OR patterns (|) to match multiple topics in ONE call:

    EFFICIENT (single call):
    - "knn|vector|embedding" - find all vector-related docs
    - "search|query|match" - find all search-related docs
    - "^Searching/|^Creating_a_table/" - multiple directories
    - "index|table|cluster" - multiple topics

    INEFFICIENT (avoid multiple calls):
    - Don't: list_documentation("knn"), then list_documentation("vector")
    - Do: list_documentation("knn|vector")  # ONE call

Returns: Filtered list of documentation files, grouped by category

Examples: # List all documentation (no filter) list_documentation()

# Find multiple topics in ONE call (RECOMMENDED)
list_documentation(search="knn|vector|embedding")
list_documentation(search="search|query|match|full-text")
list_documentation(search="index|table|cluster|replication")

# Directory-specific searches
list_documentation(search="^Searching/")  # all in Searching/
list_documentation(search="^Creating_a_table/")  # all in Creating_a_table/

# Combine directories and topics
list_documentation(search="^Searching/|^Creating_a_table/")

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
searchNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations provided, so description carries full burden. Adds valuable behavioral context: 'file list is cached, so filtering is instant and local' and describes return format ('grouped by category'). Does not explicitly state read-only/safety status, though implied by operation type.

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?

Lengthy but high information density. Structure is logical: purpose → critical usage warning → technical note → parameter details → examples. Every sentence earns its place, including the IMPORTANT call-efficiency warning which prevents API misuse.

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?

Comprehensive for tool complexity (1 param, output schema exists). Covers purpose, parameter semantics (since schema lacks them), behavioral traits (caching), and return structure. Output schema presence excuses minimal return value description.

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

Parameters5/5

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

Schema coverage is 0% (parameter has no description), but description extensively compensates: explains regex pattern support, case-insensitivity, OR syntax with pipe (|), directory prefix matching (^), and provides 6 concrete examples covering multiple use cases.

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?

Clear verb ('List') + specific resource ('documentation files from Manticore Search manual'). Distinguishes from sibling 'get_documentation' (likely retrieves content) and 'list_tables' (different domain).

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?

Excellent explicit guidance: 'Make ONE call with regex OR patterns' vs 'DO NOT make multiple calls', with concrete EFFICIENT/INEFFICIENT examples. Clearly states when to use pipe patterns versus separate calls.

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/manticoresoftware/mcp-manticore'

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