Skip to main content
Glama
Sign In
mechanic-mcp

mechanic-mcp

by lightward
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

refresh_index

Rebuild the search index from source data to ensure Mechanic task and documentation queries return current, accurate results.

Instructions

Refresh and rebuild the index from source data

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": "refresh_index"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.7

TDQS

B3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses nothing about cost, duration, downtime, permissions, or whether in-flight queries are affected during the rebuild. For a heavyweight state-changing maintenance operation, that is a significant omission.

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?

A single short sentence with the operation front-loaded and no wasted words. 'Refresh and rebuild' is slightly redundant phrasing, which keeps it just short of a 5.

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

Completeness2/5

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

The tool is simple to call, but with no annotations and no output schema, the description must convey the behavioral profile itself and does not. An agent cannot tell whether this is expensive, blocking, or safe to call repeatedly.

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?

The tool takes zero parameters, which is the baseline-4 case; there is nothing for the description to clarify beyond what the empty schema already establishes.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description pairs specific verbs (refresh, rebuild) with a resource (the index) and names the data source, so it is clear what the tool does. It does not distinguish itself from the listed siblings, but those siblings (task/doc search and retrieval) are unrelated in purpose, so the gap is minor.

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?

There is no guidance on when to invoke this versus any alternative, no prerequisites, and no indication of whether it should be run after data changes or on a schedule. The agent is left to infer all triggering conditions.

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