Skip to main content
Glama
Sign In
Agent Aggregator

Agent Aggregator

by rnd-pro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

filter__reset

Resets the active tool filter to restore the complete list of available tools from all connected servers.

Instructions

[Filter Management] Reset tool filter to show all available tools

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4.3/5.0
Behavior4/5

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

There are no annotations, so the description carries the full behavioral burden. It communicates both the state change (reset) and the resulting state (all tools visible). It does not mention persistence or reversibility, but for a zero-parameter tool this is sufficient behavioral context.

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?

A single sentence that is front-loaded with the category label and conveys the full purpose and outcome with zero wasted words. The structure is clean and immediately scannable.

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

Completeness5/5

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

For a parameterless reset operation with no output schema and no annotations, the description tells the agent everything needed to invoke it correctly: the action, the scope, and the resulting behavior. Nothing important is missing.

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 has zero parameters and the schema already fully documents this with 100% coverage. The description adds no parameter detail, but none is needed; the baseline of 4 applies for a parameterless tool.

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 ('Reset tool filter') and the expected outcome ('show all available tools'). 'Reset' is a specific verb that distinguishes this tool from siblings like filter__get and filter__update.

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

Usage Guidelines3/5

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

Usage is implied by the phrase 'show all available tools' — an agent can infer this should be called when the current filter needs to be cleared. However, the description does not explicitly state when to use this versus filter__update or filter__get, and it offers no exclusions or 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