Skip to main content
Glama
moorcheh-ai

Moorcheh MCP Server

Official
by moorcheh-ai

answer

Retrieve AI-generated answers by searching your namespace of text documents or using direct AI model calls for question answering.

Instructions

Get AI-generated answers based on data in a namespace using text queries. This tool provides intelligent, context-aware responses by searching through your stored text documents and generating comprehensive answers using advanced language models. Supports two modes: Search Mode (with namespace) and Direct AI Mode (empty namespace).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
namespaceYesNamespace to answer questions from. For Search Mode: provide a text namespace containing documents to search for context. For Direct AI Mode: provide empty string "" to make direct AI model calls without searching your data.
queryYesText query for AI answer generation. Provide a natural language question or prompt that you want the AI to answer. The AI will search through your namespace content and generate a comprehensive response based on the relevant information found.
top_kNoNumber of top results to return. Controls how many relevant documents the AI considers when generating an answer. Default is 10. Use lower values (3-5) for focused answers, higher values (8-10) for comprehensive responses that consider more context.
typeNoSearch type for answer generation. Supported value is 'text'.
thresholdNoSimilarity threshold for results. A value between 0 and 1 that filters documents based on relevance before generating the answer. Higher values (0.7-0.9) ensure only highly relevant content is used, lower values (0.3-0.5) include more context. 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 and focused answers suitable for production environments.
ai_modelNoAI model ID for answer generation (snake_case field sent to the API). Supported models: 'anthropic.claude-sonnet-4-6' (Claude Sonnet 4.6), 'anthropic.claude-opus-4-6-v1' (Claude Opus 4.6), 'meta.llama4-maverick-17b-instruct-v1:0' (Llama 4 Maverick 17B), 'amazon.nova-pro-v1:0' (Amazon Nova Pro), 'deepseek.r1-v1:0' (DeepSeek R1), 'deepseek.v3.2' (DeepSeek V3.2), 'openai.gpt-oss-120b-1:0' (OpenAI GPT OSS 120B), 'qwen.qwen3-32b-v1:0' (Qwen 3 32B), 'qwen.qwen3-next-80b-a3b' (Qwen3 Next 80B A3B). If omitted, the Moorcheh API uses its default model for your account.
chat_historyNoChat history for AI answer generation. Provide previous conversation context to help the AI maintain continuity and reference earlier parts of the conversation. This enables more coherent multi-turn conversations.
header_promptNoHeader prompt for AI answer generation. Custom instructions that define the AI's role, style, and behavior. Use this to create specialized assistants (e.g., technical support, friendly helper, formal advisor) or set specific guidelines for response generation.
footer_promptNoFooter prompt for AI answer generation. Additional instructions that are applied after the main response generation. Useful for formatting requirements, citation styles, or specific response patterns that should be consistently applied.
temperatureNoTemperature for AI answer generation. Controls the creativity and randomness of responses. Lower values (0.1-0.3) produce more focused, deterministic answers. Higher values (0.7-1.0) produce more creative, varied responses. Default is 0.7.
Behavior3/5

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

No annotations provided, so the description carries full burden. It discloses the two operational modes and explains that the tool searches documents and generates answers. However, it does not mention whether the operation is read-only, any side effects like consumption of AI credits, or potential latency. Lacks details on authentication or rate limits. Adequate but not thorough.

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?

Reasonably concise, with purpose stated upfront. Two short paragraphs. Some redundancy (e.g., 'Get AI-generated answers' and 'provides intelligent, context-aware responses' are similar). Could be slightly tighter, but overall well-structured for a tool with many parameters.

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?

Given 11 parameters and no output schema, the description covers the two modes and parameter semantics well. However, it does not describe the return value or response format, which is a notable gap. For completeness, it should state what the AI generates (e.g., a string answer) or mention any pagination. Error cases or prerequisites (e.g., namespace must contain data) are not addressed.

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?

Schema coverage is 100%, so baseline is 3. The description adds significant value beyond the schema: explains the dual purpose of namespace, defaults for top_k, condition for threshold, lists specific model IDs with names, clarifies role and content in chat_history, and distinguishes header/footer prompts. This goes beyond the schema 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?

States exactly what the tool does: 'Get AI-generated answers based on data in a namespace using text queries.' Clearly explains two modes (Search vs Direct AI) which distinguishes it from sibling tools like 'search' that retrieve raw data. The purpose is specific and contrasts effectively with nearby tools.

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?

Provides clear guidance on when to use each mode (namespace for search-based answers, empty string for direct AI). While it doesn't explicitly contrast with sibling tools, the description implies usage for generated answers vs raw search. Could be improved by explicitly stating when not to use this tool (e.g., for raw document retrieval, use 'search' instead).

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