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

@aiwerk/mcp-server-elevenlabs

by AIWerk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

set_third_party_disabling_policy

Configure the workspace policy that controls whether third-party integrations can be disabled.

Instructions

Set Workspace Third-Party Disabling Policy

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

Input Schema

NameRequiredDescriptionDefault
third_party_disable_allowedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.3/5.0
Behavior1/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false, and the description adds nothing beyond them—no statement of scope, reversibility, or what disabling/enabling implies. For a workspace-wide security policy mutation, this is a serious gap with no compensating context.

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 short and front-loaded, but it is under-specified rather than concise—it contributes no information beyond the name. Length is fine; content is absent.

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

Completeness1/5

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

No output schema, no annotations covering semantics (only safety hints), and a critical untyped boolean parameter leave the definition inadequate for an agent to invoke this workspace security-policy tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one parameter, `third_party_disable_allowed`, with 0% schema description coverage and no explanation in the description. An agent cannot tell what true vs false does (allow disabling? disable third-party apps?) or whether the parameter is optional-with-default, since required count is 0.

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 simply restates the tool name/title verbatim ('Set Workspace Third-Party Disabling Policy') with no added detail about what the policy governs or what setting it means. It is effectively a tautology of the identifier, with no differentiation from the many other `set_*`/`update_*` siblings.

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

Usage Guidelines1/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, what prerequisites exist, or what alternatives (e.g. update_settings_route, update_mcp_server_approval_policy_route) might apply. An agent has no basis to choose this tool over its siblings.

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