Skip to main content
Glama

retell_get_knowledge_base

Retrieve configuration details for a knowledge base to access structured information within the Retell AI platform.

Instructions

Retrieve a knowledge base configuration.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
knowledge_base_idYesThe knowledge base ID

Implementation Reference

  • Handler implementation for the retell_get_knowledge_base tool. It extracts the knowledge_base_id from arguments and makes a GET request to the Retell API's get-knowledge-base endpoint.
    case "retell_get_knowledge_base":
      return retellRequest(`/get-knowledge-base/${args.knowledge_base_id}`, "GET");
  • Schema definition for the retell_get_knowledge_base tool, including name, description, and input schema requiring knowledge_base_id.
    {
      name: "retell_get_knowledge_base",
      description: "Retrieve a knowledge base configuration.",
      inputSchema: {
        type: "object",
        properties: {
          knowledge_base_id: {
            type: "string",
            description: "The knowledge base ID"
          }
        },
        required: ["knowledge_base_id"]
      }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'Retrieve' but doesn't clarify if this is a read-only operation, what permissions are needed, how errors are handled, or what the response format looks like. This leaves significant gaps in understanding the tool's behavior beyond the basic action.

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 directly states the tool's purpose without any wasted words. It's front-loaded and appropriately sized for a simple retrieval operation, making it easy to parse quickly.

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?

Given the lack of annotations and output schema, the description is incomplete for a retrieval tool. It doesn't explain what 'configuration' entails, the return format, or any behavioral aspects like error handling. For a tool with no structured support, more context is needed to be fully helpful.

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 input schema has 100% description coverage, with the parameter 'knowledge_base_id' clearly documented. The description doesn't add any extra meaning beyond the schema, such as format examples or constraints, so it meets the baseline for high schema coverage without compensating value.

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 ('Retrieve') and resource ('knowledge base configuration'), which is specific and unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'retell_list_knowledge_bases' or 'retell_get_agent', which might also retrieve knowledge-related information, leaving some room for improvement in sibling distinction.

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. It doesn't mention when to choose this over 'retell_list_knowledge_bases' for listing all bases or 'retell_get_agent' for agent-specific knowledge, nor does it specify prerequisites or context for usage.

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