Skip to main content
Glama
brandon-fryslie

elevenlabs-mcp

check_subscription

Read-only

Check your current subscription status to monitor API usage and manage your account effectively.

Instructions

Check the current subscription status. Could be used to measure the usage of the API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYes
textYes
annotationsNo
_metaNo

Implementation Reference

  • Registration of the 'check_subscription' tool via the @mcp.tool decorator with readOnlyHint and description.
    @mcp.tool(
        annotations=ToolAnnotations(readOnlyHint=True, openWorldHint=True),
        description="Check the current subscription status. Could be used to measure the usage of the API."
    )
  • Handler function for 'check_subscription'. Calls client.user.subscription.get() and returns the JSON-serialized subscription data as TextContent.
    def check_subscription() -> TextContent:
        subscription = client.user.subscription.get()
        return TextContent(type="text", text=f"{subscription.model_dump_json(indent=2)}")
  • The 'client' variable (ElevenLabs client) used by check_subscription to call the subscription API.
    client = ElevenLabs(api_key=api_key, httpx_client=custom_client, base_url=origin)
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint. The description adds that it checks current status and hints at measuring usage, which complements annotations without contradiction. No additional behavioral traits beyond what annotations provide.

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?

Two sentences, front-loaded with the primary action ('Check the current subscription status'), no redundant information. Every word earns its place.

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

Completeness5/5

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

Given zero parameters, presence of an output schema, and annotations covering readOnly and openWorld, the description adequately explains the tool's purpose and potential use. No gaps.

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 has no parameters, so the description is not required to explain them. Baseline 4 applies, and the description adds no confusion.

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 explicitly states the tool checks subscription status, a distinct function not overlapping with any sibling tools (e.g., speech, voice, agents). The verb 'check' and resource 'subscription' are specific and clear.

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

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description suggests a use case ('measure the usage of the API'), providing context for when to invoke this tool. No explicit exclusions or alternatives are needed since no sibling tool addresses subscription.

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/brandon-fryslie/vibedungeon-voice'

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