Skip to main content
Glama

hebcal

by io.github.hebcal

daf-yomi

Calculates the Daf Yomi (Babylonian Talmud) learning for a specified date

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesGregorian date in yyyy-MM-dd format

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observed

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations provided, the description carries the full behavioral disclosure burden. It clarifies the Babylonian Talmud variant but does not mention what the return value looks like, edge cases, date validity constraints, or whether the operation is purely read-only.

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 one short, front-loaded sentence that directly communicates the tool's core function. There is no filler or redundant wording.

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 one-parameter calculation tool, the description is minimally adequate, but it does not specify the output format or clarify what 'learning' means in concrete terms. This gap matters because there is no output schema to fill it.

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 fully describes the single 'date' parameter with format yyyy-MM-dd, so schema coverage is 100%. The description adds no additional parameter meaning, which matches the baseline for well-documented schemas.

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 and resource: it calculates Daf Yomi (Babylonian Talmud) learning for a date. It is clear and unique among the sibling tools, though it does not explicitly name or differentiate against them.

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 date-driven scope implies when to use the tool, and the Daf Yomi resource is conceptually distinct from the sibling tools. However, there is no explicit when-to-use, when-not-to-use, or alternative routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All hebcal toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: two cover bidirectional date conversion, while the others handle unique calendar computations like holidays, Torah portions, Shabbat times, Daf Yomi, and Yahrzeit. There is no overlap or ambiguity between them.

Naming Consistency4/5

All tool names use lowercase hyphenated words, creating a uniform style. However, some names are verb-led (convert-gregorian-to-hebrew) while others are noun-led (daf-yomi, shabbat-times), which is a minor deviation from a single naming pattern but remains readable and predictable.

Tool Count5/5

With 7 tools, the server is well-scoped for a Jewish calendar domain. Each tool addresses a distinct functionality, and the count fits comfortably within the ideal range for a focused utility server.

Completeness4/5

The server covers the core Jewish calendar needs: date conversion, annual holidays, Shabbat times, Torah portions, Daf Yomi, and Yahrzeit. A minor gap is the lack of a tool for a specific holiday date lookup (without retrieving the whole year) or more advanced halachic time calculations, but these are workable gaps.

Resources