Skip to main content
Glama
Sign In
@aiwerk/mcp-server-elevenlabs

@aiwerk/mcp-server-elevenlabs

by AIWerk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

remove_mcp_server_tool_approval_route

DestructiveIdempotent

Removes approval for an MCP server tool by specifying the server ID and tool name, so the tool no longer requires approval.

Instructions

Delete Mcp Server Tool Approval

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": {
      "mcp_server_id": "<mcp_server_id>",
      "tool_name": "<tool_name>"
    },
    "name": "remove_mcp_server_tool_approval_route"
  }
}

Input Schema

NameRequiredDescriptionDefault
tool_nameYesName of the MCP tool to remove approval for.
mcp_server_idYesID of the MCP Server.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered structurally. However, the description adds nothing beyond that — no statement about what is destroyed (the approval route only, not the server or tool), required permissions, or effect on in-flight approvals.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is technically brief, but there is no real content to be concise about; the single phrase duplicates the name/title rather than front-loading useful information. This is under-specification rather than effective conciseness.

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?

For a destructive two-parameter mutation with no output schema, the description should at minimum identify the target resource and the scope of deletion. Rich annotations carry the safety signal, but the text itself leaves behavioral and routing context entirely unstated.

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 description coverage is 100%, with both mcp_server_id and tool_name clearly documented in the schema itself. Per the rubric, a high-coverage schema sets the baseline at 3 even though the description contributes no parameter detail.

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

Purpose2/5

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

The description 'Delete Mcp Server Tool Approval' is essentially a restatement of the tool name and annotation title, providing no additional specification of what deletion means in this context (removing an approval route for a specific tool on a specific MCP server). It is not misleading, but it is tautological rather than clarifying.

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 guidance on when to use this tool versus siblings such as add_mcp_server_tool_approval_route, update_mcp_server_approval_policy_route, or remove_mcp_tool_config_override_route. The agent must infer the invocation context from the name alone.

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