Skip to main content
Glama

retell_get_concurrency

Check current concurrent call limits and usage for your Retell AI account to monitor agent capacity and manage call volume effectively.

Instructions

Check the current concurrent call limits and usage for your account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The execution handler for the 'retell_get_concurrency' tool. It makes a GET request to the Retell API's '/get-concurrency' endpoint with no arguments.
    case "retell_get_concurrency":
      return retellRequest("/get-concurrency", "GET");
  • Tool schema definition including name, description, and empty input schema (no required parameters).
      name: "retell_get_concurrency",
      description: "Check the current concurrent call limits and usage for your account.",
      inputSchema: {
        type: "object",
        properties: {}
      }
    },
  • src/index.ts:1084-1090 (registration)
    The tool is registered in the 'tools' array used by the ListToolsRequestHandler.
      name: "retell_get_concurrency",
      description: "Check the current concurrent call limits and usage for your account.",
      inputSchema: {
        type: "object",
        properties: {}
      }
    },
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states the tool checks limits and usage, implying a read-only operation, but doesn't disclose behavioral traits such as authentication requirements, rate limits, response format, or whether it provides real-time or cached data.

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, efficient sentence that front-loads the core purpose without any wasted words. It directly communicates what the tool does in a clear and structured manner.

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

Completeness3/5

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

Given the tool's complexity (simple read operation with no parameters) and lack of annotations or output schema, the description is minimally adequate. It states the purpose but lacks details on behavior, response format, or error handling, leaving gaps for an AI agent to infer.

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 tool has 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description appropriately omits parameter details, earning a baseline score of 4 for not adding unnecessary information.

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 specific action ('Check') and resource ('current concurrent call limits and usage for your account'), distinguishing it from sibling tools that focus on creating, deleting, or updating various entities rather than retrieving account-level usage metrics.

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?

No explicit guidance on when to use this tool versus alternatives is provided. The description implies usage for monitoring account limits, but it doesn't specify prerequisites, frequency, or contrast with other tools like retell_list_calls or retell_get_call for related information.

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/itsanamune/retellsimp'

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