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

@aiwerk/mcp-server-elevenlabs

by AIWerk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_environment_variable

Read-onlyIdempotent

Fetch a specific environment variable's value by ID from the ElevenLabs MCP server to access stored configuration and API settings.

Instructions

Get Environment Variable

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": {
      "env_var_id": "<env_var_id>"
    },
    "name": "get_environment_variable"
  }
}

Input Schema

NameRequiredDescriptionDefault
env_var_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that—no mention of what is returned, error conditions, or scope. With annotations doing the heavy lifting, the description could still add value but doesn't.

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

Conciseness3/5

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

The description is a single short phrase with no waste, but it's too terse to be useful. It is appropriately sized for what it says, but what it says is minimal.

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 simple getter with one required parameter and no output schema, the description is incomplete. It doesn't explain what the tool returns, whether it's by ID or name, or how it relates to other environment variable tools. The agent lacks sufficient context to invoke it confidently.

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

Parameters2/5

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

The schema has 1 parameter (env_var_id) with 0% description coverage. The description doesn't mention the parameter at all, so it fails to compensate for the lack of schema documentation. The agent must guess what env_var_id represents and its format.

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

Purpose3/5

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

The description 'Get Environment Variable' states a verb ('Get') and resource ('Environment Variable'), which is clear enough. However, it simply restates the tool name and title verbatim, providing no additional differentiation from siblings like list_environment_variables. It's minimally viable but not informative beyond the name.

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 alternatives such as list_environment_variables or update_environment_variable. The description offers no context about when retrieval is appropriate, leaving the agent to infer.

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