Skip to main content
Glama

retell_end_chat

Terminate an active chat session to manage conversation flow and free up resources on the Retell AI platform.

Instructions

End an active chat session.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chat_idYesThe chat session ID to end

Implementation Reference

  • Handler implementation for retell_end_chat tool: sends PATCH request to Retell API /end-chat endpoint with provided arguments.
    case "retell_end_chat":
      return retellRequest("/end-chat", "PATCH", args);
  • Input schema for retell_end_chat tool defining the required chat_id parameter.
      name: "retell_end_chat",
      description: "End an active chat session.",
      inputSchema: {
        type: "object",
        properties: {
          chat_id: {
            type: "string",
            description: "The chat session ID to end"
          }
        },
        required: ["chat_id"]
      }
    },
  • src/index.ts:1283-1285 (registration)
    Registration of the tools list handler which includes the retell_end_chat tool schema in the returned tools array.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return { tools };
    });
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It states the action is to 'end' a session, implying a destructive operation, but doesn't clarify if this is reversible, what happens to chat data, or if specific permissions are required. This leaves significant gaps for a mutation tool.

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, direct sentence with zero wasted words. It's front-loaded with the core action and resource, making it highly efficient and easy to parse.

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 operation with no annotations and no output schema, the description is inadequate. It lacks critical context such as what 'ending' entails (e.g., data deletion, session termination), error conditions, or response format, leaving the agent under-informed about tool behavior.

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?

The schema description coverage is 100%, with the single parameter 'chat_id' well-documented in the schema. The description adds no additional parameter context beyond what the schema already provides, so it meets the baseline score of 3 for high schema coverage.

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

Purpose4/5

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

The description clearly states the action ('End') and resource ('an active chat session'), making the purpose immediately understandable. However, it doesn't differentiate this tool from sibling tools like 'retell_delete_chat' or 'retell_delete_call', which might have overlapping functionality.

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?

The description provides no guidance on when to use this tool versus alternatives like 'retell_delete_chat' or 'retell_update_call' for ending chats. There's no mention of prerequisites (e.g., chat must be active) or consequences, leaving the agent without context for proper tool selection.

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