Skip to main content
Glama

clear_queue

Clear the audio playback queue to cancel pending text-to-speech synthesis tasks and stop scheduled voice playback.

Instructions

再生キューをクリア

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The actual implementation of the clear() method that clears the queue. It clears the shared state for the client and empties the tasks array.
    async clear(): Promise<void> {
      // キューに残っているタスクの共有状態を削除
      try {
        await this.sharedState.clearAllUsageForClient();
      } catch (error) {
        console.error("Failed to clear shared state:", error);
      }
      
      this.tasks = [];
    }
  • The handler case for 'clear_queue' tool that calls queue.clear() and returns a success message in Japanese.
    case "clear_queue": {
      await queue.clear();
      return {
        content: [
          {
            type: "text",
            text: "キューをクリアしました",
          },
        ],
      };
    }
  • src/index.ts:106-113 (registration)
    The tool registration for 'clear_queue' with description and empty input schema.
    {
      name: "clear_queue",
      description: "再生キューをクリア",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • The input schema for clear_queue tool - an empty object with no properties.
    inputSchema: {
      type: "object",
      properties: {},
    },
Behavior2/5

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

No annotations are provided, yet the description fails to disclose critical behavioral traits of this destructive operation, such as whether clearing affects the currently playing item, if the action is reversible, or what permissions are required. It states the action without explaining state impact or side effects.

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?

The description consists of a single three-word Japanese phrase with zero redundant text or wasted structure. However, given the lack of annotations and the destructive nature of the operation, the extreme brevity may be insufficient rather than optimally concise.

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?

As a state-mutating tool with no annotations, no output schema, and undocumented behavioral implications, the description leaves significant gaps regarding what exactly gets cleared and the consequences of invocation. It meets the bare minimum of stating the action but lacks necessary operational context for safe usage.

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 input schema contains zero parameters, establishing a baseline score of 4 per the evaluation rules. The description correctly omits parameter details since none exist to document.

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 states '再生キューをクリア' (clear the playback queue), providing a specific verb and resource that aligns with the tool name. While it clarifies that 'queue' refers specifically to the playback queue, it does not explicitly differentiate this tool from sibling operations like `say` (which likely adds items) or `get_queue_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 offers no guidance on when to invoke this tool versus alternatives, nor does it mention prerequisites or side effects. There is no indication of whether this should be used before `say` operations, during active playback, or only when the queue is in a specific state.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/arrow2nd/vv-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server