Skip to main content
Glama

reset_intellisearch

Resets the current project's IntelliSearch analysis, clearing prior results so a new analysis can run from a clean state.

Instructions

Reset the project's IntelliSearch analysis.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, so the agent knows it mutates state but is not flagged destructive. The description adds nothing about what is discarded by a 'reset', whether prior analysis results or configuration are lost, whether it is reversible, or how long it takes — and 'reset' arguably sits in mild tension with destructiveHint=false, which deserves clarification.

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, front-loaded sentence with no filler or redundancy. It is efficiently sized, though its brevity comes at the cost of information rather than being optimally informative.

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?

With no output schema and annotations that only cover safety hints, the description must carry the full burden of explaining the effect of this mutation. It does not say what state is reset, what the resulting state looks like, or what the caller should expect afterwards, which is insufficient for a state-changing tool.

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, so the schema carries no semantics to supplement and the baseline is 4. The description does not need to explain parameters, though it could clarify that the project is implied by session context.

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

Purpose3/5

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

The description names a specific verb ('Reset') and a scoped resource ('the project's IntelliSearch analysis'), so the agent knows it is a state-clearing action on something called IntelliSearch. However, 'IntelliSearch analysis' is an undefined domain term and the sentence does nothing to distinguish this tool from siblings or explain what the analysis actually is, leaving the purpose only vaguely grasped.

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 indication of when to call this tool versus alternatives, no prerequisites, and no note about when resetting is appropriate or discouraged. The agent must infer usage entirely.

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