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

@aiwerk/mcp-server-elevenlabs

by AIWerk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_rag_indexes

Read-onlyIdempotent

Fetches RAG indexes for a specified knowledgebase document using its document ID, allowing you to review or manage the document's retrieval setup.

Instructions

Get Rag Indexes Of The Specified Knowledgebase Document.

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": {
      "documentation_id": "<documentation_id>"
    },
    "name": "get_rag_indexes"
  }
}

Input Schema

NameRequiredDescriptionDefault
documentation_idYesThe id of a document from the knowledge base. This is returned on document addition.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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 further — no note on what the indexes represent, whether an empty result is possible, or how it relates to index creation.

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

Conciseness4/5

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

A single, front-loaded sentence with no wasted words. It is efficient, though the title-case phrasing and lack of any routing clause keep it from being exemplary.

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?

For a simple one-parameter read tool with no output schema and strong annotations, this is minimally adequate. It leaves the return shape (a list of RAG indexes) and the distinction from get_or_create_rag_indexes unaddressed.

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?

Schema coverage is 100% and the single documentation_id parameter is fully documented in the schema. The description's phrase 'Specified Knowledgebase Document' corroborates the parameter but adds no syntax, format, or sourcing detail beyond what the schema already states.

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 states a specific verb ('Get') and resource ('RAG Indexes') scoped to a knowledgebase document, which is clearer than a bare name restatement. However, it does not differentiate itself from near-identical siblings such as get_or_create_rag_indexes, get_rag_index_overview, or rag_index_status.

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 when-to-use guidance, no prerequisites, and no mention of when a caller should prefer this over get_or_create_rag_indexes or rag_index_status. The agent must infer selection purely from the name.

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