get_versions
Returns available text versions for a specific reference
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| ref | Yes | The text reference (e.g., 'Genesis.1.1') |
Sefaria Library
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A3.6/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the full behavioral burden. It only states what is returned, offering no details on side effects, permissions, error cases, pagination, or other behavioral traits. This is a significant gap for a tool with no annotation safety hints.
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 concise sentence that communicates the core function without any redundant words or filler. It is front-loaded with the verb and resource, making it easy to parse quickly.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (one parameter, no nested objects, no output schema), the description adequately conveys the tool's purpose. However, it lacks detail about the structure of 'available text versions' and any edge cases, which slightly lowers completeness. For a simple read tool, it is sufficient but not exhaustive.
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 description coverage is 100% since 'ref' is fully described as 'The text reference (e.g., 'Genesis.1.1')'. The description's phrase 'for a specific reference' adds no extra meaning beyond the schema, 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.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses the verb 'Returns' with a specific resource 'available text versions' scoped to 'a specific reference', making it clearly distinct from sibling tools like get_calendars or get_text. It precisely states what the tool does.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage when text versions are needed for a reference, but it provides no explicit guidance on when to choose this over alternatives. No exclusions or comparisons to sibling tools are mentioned, leaving the selection criteria implicit.
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.