Skip to main content
Glama
moorcheh-ai

Moorcheh MCP Server

Official
by moorcheh-ai

search

Find relevant content across namespaces using natural language queries or vector similarity. Filter results by metadata or keywords for precise discovery.

Instructions

Search for data in a namespace using semantic search or vector similarity. This tool provides powerful search capabilities across your namespaces, supporting both text-based semantic search and vector-based similarity search. For text search, you can use natural language queries to find relevant documents based on meaning rather than just keywords. For vector search, you can find similar content by comparing vector embeddings. The tool supports advanced features like result filtering, similarity thresholds, metadata filters, keyword filters, and kiosk mode for production environments. This is ideal for building intelligent search interfaces, recommendation systems, or content discovery features.

Filtering Capabilities:

  • Metadata Filters: Use #key:value format (e.g., #category:tech, #priority:high)

  • Keyword Filters: Use #keyword format (e.g., #important, #urgent)

  • Filters only apply to text search and metadata must be manually uploaded with documents

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
namespacesYesNamespaces to search in. Provide an array of namespace names where you want to search for content. You can search across multiple namespaces simultaneously. All namespaces must be accessible with your API key.
queryYesSearch query. For text search: provide a natural language query string (e.g., 'tell me about the company?', 'how to configure authentication?'). For vector search: provide an array of numbers representing a vector embedding (e.g., [0.1, 0.2, 0.3, ..., 0.768]). The query type will be automatically detected based on the input format. DO NOT USE QUOTES IN THE QUERY FOR VECTOR SEARCH. Filtering: For text search, you can include filters in your query: - Metadata filters: #category:tech #priority:high - Keyword filters: #important #urgent - Combine both: 'serverless benefits #category:tech #important'
query_typeNoType of query to perform. 'text' for semantic search using natural language queries. 'vector' for similarity search using vector embeddings. If not specified, the type will be automatically detected based on the query format (string for text, array for vector).
top_kNoNumber of top results to return. Controls how many search results are returned, with higher values providing more comprehensive results. Default is 10. Use lower values (3-5) for focused results, higher values (10-20) for broader exploration.
thresholdNoSimilarity threshold for results. A value between 0 and 1 that filters results based on similarity score. Higher values (0.7-0.9) return only highly similar results, lower values (0.3-0.5) return more comprehensive results. Required when kiosk_mode is true.
kiosk_modeNoKiosk mode for restricted search. When true, search is restricted to specific namespaces with threshold filtering, providing more controlled results suitable for production environments. When false, search across all specified namespaces without strict filtering.
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses auto-detection of query type, behavior of filters, kiosk mode, and threshold requirements. It also warns against using quotes for vector search. However, it omits rate limits or authentication details.

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?

The description is well-structured with a summary and then detailed sections. While slightly verbose, each sentence adds value. It is front-loaded with the core purpose.

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?

No output schema is provided, and the description does not describe the structure of search results (e.g., scores, metadata). For a search tool of moderate complexity, describing the return format would enhance completeness.

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 description coverage is 100%, but the description adds significant value by explaining query auto-detection, filter syntax (metadata/keyword), top_k usage recommendations, threshold range and kiosk mode purpose. This goes well beyond the schema's basic descriptions.

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 the tool searches data using semantic or vector similarity, and it distinguishes itself from siblings like get-data or fetch-text-data by focusing on search vs direct retrieval. It provides specific use cases like building search interfaces, recommendation systems.

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?

The description explains when to use text versus vector search and describes filtering capabilities, but does not explicitly state when not to use this tool in favor of siblings like 'answer' or 'get-data'. It provides contextual guidance for usage scenarios.

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/moorcheh-ai/moorcheh-mcp'

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