Skip to main content
Glama
alopez3006

snipara-mcp

by alopez3006

snipara_context_query

Read-onlyIdempotent

Query project documents and business files to retrieve source-grounded answers and context. Returns ranked sections, retrieval diagnostics, and an answer pack with verification checks.

Instructions

Query project documents, parsed business files, and shared context. Use this first for source truth and narrative documentation. Returns a source-grounded answer_pack plus retrieval_diagnostics and ranked sections within token budget. If a broad query times out, retry once with a narrow 3-8 term query, max_tokens 800-1500, search_mode='keyword', return_references=true, auto_decompose=false, and include_all_tiers=false. For exact text use snipara_search; for structural code context use snipara_code_neighbors, snipara_code_callers, or snipara_code_imports.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskNoOptional task label that scopes the live-join fallback and retrieval correlation; persisted outcome posterior statistics remain project-wide
queryYesDocumentation, business-context, or current-truth question. For timeout recovery, narrow this to the key file, feature, symbol, or 3-8 terms.
max_tokensNoToken budget. Use 800-1500 for fast recovery retries after a timeout.
search_modeNoSearch strategy. Use keyword for fast retry/recovery paths; use hybrid for normal documentation discovery.hybrid
auto_decomposeNoAuto-decompose complex queries into sub-queries (Pro+ only). Complex queries (50+ words, multiple questions, comparisons) are automatically broken down and results merged. Set to False for fast timeout recovery retries.
include_metadataNoInclude document, section, tier, and retrieval metadata with returned context.
prefer_summariesNoPrefer stored summaries when available without excluding authoritative source matches.
include_all_tiersNoInclude all context tiers including COLD and ARCHIVE. By default, searches only HOT and WARM tiers for faster, more relevant results.
return_referencesNoReturn chunk references (IDs + previews) instead of full content. Use snipara_get_chunk to retrieve full content by ID. Reduces hallucination by maintaining clear source attribution and is the preferred fast retry path after a timeout.
correlation_contextNoOptional retrieval-correlation context. Reuse session_id across retrieval and outcome calls so telemetry can be joined inside the authenticated project. These identifiers never change authorization or project scope; do not include secrets, tenant IDs, or user data.
include_answer_packNoInclude a structured answer pack with source facts, caveats, verification checklist, and code/context hints before the ranked context sections.
context_chunk_outcome_rerank_modeNoRequested bounded chunk-outcome rerank mode. This request can disable or lower the server-configured mode but cannot escalate beyond it.disabled
context_chunk_outcome_window_hoursNoStrict attribution window for compatible chunk outcomes.
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds behavioral details like timeout recovery, token budget behavior, and fallback to job queue. This goes beyond what annotations provide, though some redundancy exists.

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 front-loaded with primary purpose, then flows to usage, recovery, and alternatives. It is appropriately sized for a complex tool with 13 parameters, though some repetition in parameter details could be streamlined.

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?

Despite no output schema, the description explains return types (answer_pack, diagnostics, ranked sections) and covers timeout behavior, retry logic, token budget, and sibling tools. It addresses the complexity of nested parameters and provides sufficient context for an agent to use the tool effectively.

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 extra meaning by contextualizing several parameters (query, max_tokens, search_mode, return_references, auto_decompose, include_all_tiers) within the timeout recovery scenario, enhancing their practical use beyond 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?

The description clearly states the tool queries project documents, business files, and shared context for source truth and narrative documentation. It specifies the return type (answer_pack, diagnostics, ranked sections) and distinguishes from siblings by directing exact text searches to snipara_search and code queries to code-specific tools.

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?

Explicit guidelines are provided: 'Use this first for source truth and narrative documentation.' A recovery strategy for timeouts is given in detail (narrow query, max_tokens 800-1500, etc.), and alternatives are named for exact text (snipara_search) and code context (snipara_code_* tools).

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/alopez3006/snipara-mcp'

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