Skip to main content
Glama
alopez3006

snipara-mcp

by alopez3006

rlm_reindex

Trigger or poll a reindex job to rebuild documentation or code indexes after large syncs when index coverage is low or documents are missing chunks.

Instructions

Trigger a project reindex job or poll an existing reindex job.

Use this when index coverage is low, documents are missing chunks, or you need to rebuild documentation/code indexes after large sync operations. Call without job_id to create a job, or pass job_id to check progress via MCP.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
job_idNoExisting reindex job ID to poll instead of creating a new one
modeNoReindex mode when creating a new jobincremental
kindNoWhich index to rebuild when creating a new jobdoc
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses the two modes (trigger vs poll) but lacks details on destructive effects, rate limits, or permissions. This is adequate but has gaps.

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

Conciseness5/5

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

The description is extremely concise, with two sentences and a usage hint. Every sentence adds value, and it is front-loaded with the key action.

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?

Complexity is moderate. No output schema, so description should explain return info. It mentions 'check progress via MCP' but not format or statuses. Prerequisites like project existence are omitted.

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

Parameters3/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 no extra meaning beyond what the schema already provides for the parameters.

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 triggers or polls a reindex job, specifying the resource and action. It distinguishes from siblings like rlm_index_health by focusing on reindexing.

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 provides explicit scenarios for use (low coverage, missing chunks, post-sync rebuild) and how to invoke (with/without job_id). However, it does not mention when not to use or alternatives.

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