Skip to main content
Glama
Sign In
Simple Voice MCP Server

Simple Voice MCP Server

by Kurasuai-Inc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

remove_from_dictionary

Remove specified English words from the custom pronunciation dictionary. Supports removing multiple words by using comma separation.

Instructions

カスタム辞書から指定した英単語のエントリを削除します。複数削除する場合はカンマ区切りで指定できます。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "english": "<english>"
    },
    "name": "remove_from_dictionary"
  }
}

Input Schema

NameRequiredDescriptionDefault
englishYes削除する英単語。複数の場合はカンマ区切り（例: hdmi,api,.py または test,1つ,2つ）

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/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 full burden. It discloses the deletion behavior and comma-separated input. However, it does not mention what happens if the word does not exist, or if there are any irreversible side effects. The destructive nature is implied but not fully detailed.

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?

The description is a single, concise sentence that front-loads the verb (削除します/delete). No unnecessary words or redundancy.

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?

For a simple tool with one parameter, no output schema, and no nested objects, the description is largely complete. It explains the action and input format. It could mention whether deletion is permanent or if there is a confirmation step, but overall adequate for the agent to invoke correctly.

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% (single parameter with description). The description adds the comma separation detail but does not provide significant meaning beyond the schema. With high coverage, 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 (削除する/delete) and the resource (カスタム辞書/custom dictionary). It also specifies that multiple entries can be deleted with comma separation. This clearly distinguishes it from sibling tools like add_to_dictionary (adds) and list_dictionary (lists).

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?

The description does not explicitly state when to use this tool versus alternatives. However, the function is implied by the name and sibling tools: use for deletion, not for adding or listing. No exclusions or prerequisites are mentioned.

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