get_index
Returns metadata for a specific text, such as section names and categories
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| v2 | No | Use v2 index for more detailed records | |
| title | Yes | The title of the text (e.g., 'Genesis') |
Sefaria Library
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
B3.1/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Since there are no annotations, the description carries the full burden of behavioral disclosure. It only states the output type and does not mention error handling, side effects, authorization requirements, or runtime behavior, leaving significant gaps.
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 sentence that is front-loaded with the core action and resource. It includes useful examples without any filler or redundant information.
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?
With no output schema, the description provides only illustrative examples of the metadata. It lacks information about return structure, error conditions, or how to choose this tool over its siblings, leaving noticeable gaps for an AI agent.
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 already provides 100% coverage with descriptions for both parameters (title and v2). The tool description does not add any additional meaning or usage details for the parameters, so the baseline score of 3 is appropriate.
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 provides a specific verb ('Returns') and resource ('metadata for a specific text') with concrete examples like 'section names and categories'. However, it does not explicitly differentiate from sibling tools such as get_toc or get_topics, so it loses one point.
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 guidance is given on when to use this tool versus the many sibling get_* tools. It only states what the tool does, with no exclusions, alternatives, or contextual hints.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.8/5.0
Disambiguation5/5
Each tool targets a distinct aspect of the library: schedules, text metadata, links, structure, content, TOC, topics, versions, and search. There is no meaningful overlap that would cause an agent to select the wrong tool.
Naming Consistency5/5
All tools follow a consistent verb_noun snake_case pattern, with 'get_' for retrieval operations and 'search_texts' for the search operation. The naming style is uniform and predictable.
Tool Count5/5
With 9 tools, the server is well-scoped for a read-only library API. Each tool earns its place, covering the core retrieval needs without overwhelming the agent with excessive options.
Completeness5/5
The set comprehensively covers the library domain: searching, retrieving text, versions, structure, links, calendars, topics, and the full table of contents. For a read-only library, there are no obvious missing operations or dead ends.