Skip to main content
Glama
Sign In
mcp-semantic-search

mcp-semantic-search

by lemuelflores
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

index

Create a semantic search index of local markdown specifications, skipping unchanged content unless force re-index is requested.

Instructions

Index the specs/ directory in the current project (app). Automatically skips if content hasn't changed since last index.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "index"
  }
}

Input Schema

NameRequiredDescriptionDefault
reindexNoForce re-index even if content unchanged (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Discloses the auto-skip behavior (content unchanged). Without annotations, the description carries the burden; it provides one key behavioral trait but no details on effects, auth, or rate limits.

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?

Two sentences, zero wasted words, highly efficient. Key information is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a low-complexity tool (one optional param, no output schema), the description adequately covers purpose and behavior. Lacks explicit linkage to sibling tools, but overall sufficient.

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 covers the single parameter 'reindex' with a description; the tool description adds no extra meaning beyond reinforcing the auto-skip context. With 100% schema coverage, baseline 3 is appropriate.

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?

Explicitly states 'Index the specs/ directory' (specific verb+resource). Clearly distinguishes from siblings 'search' and 'status' by its indexing action.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives like 'search' or 'status'. Does not mention prerequisites or exclusion criteria.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools