Skip to main content
Glama
Sign In
sifs

sifs

by tristanmanchester
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

clear_index

Remove a selected source from the in-memory MCP cache. The next search or status call rebuilds or reloads the cache.

Instructions

Remove the selected source from the in-memory MCP cache. The next search or status call rebuilds or reloads it.

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

Input Schema

NameRequiredDescriptionDefault
profileNoSaved profile to use for source defaults.
sourceNoGit URL or local path. Omit only when the server has a default source.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the rebuild behavior but does not elaborate on scope (e.g., memory vs disk), side effects, or required permissions.

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, front-loaded with the main action, no wasted words.

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?

Given no output schema and no annotations, the description is fairly complete for a simple removal tool. It explains the action and the rebuild consequence, though could mention when to use it.

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% with both parameters described in the schema. The description does not add additional meaning beyond 'selected source', so 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?

The description clearly states the action ('Remove the selected source from the in-memory MCP cache') and distinguishes from siblings like 'refresh_index' and 'index_status' by specifying removal rather than refresh or status.

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?

The description mentions the consequence ('next search or status call rebuilds or reloads it') but does not provide explicit guidance on when to use this tool versus alternatives like 'refresh_index' or any exclusions.

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