Skip to main content
Glama

Besorah — the Bible in Hebrew, Greek, Aramaic and English

Weekly Torah portion

get_parashah
Read-onlyIdempotent

Returns a weekly Torah portion: its name, Hebrew name, meaning and Shabbat date, with its Torah, Haftarah and Besorah (New Testament) readings and links, on the Diaspora calendar. Give a name ('Toledot'), a date (YYYY-MM-DD) for the portion read on the Shabbat on or after it, or list=true for every portion; with none, this week's. Use when the user asks about a weekly Torah portion, its Haftarah or its New Testament reading.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_parashah"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoa date as YYYY-MM-DD; gives the portion read on the Shabbat on or after it
listNotrue returns every portion
nameNoportion name, e.g. Toledot
formatNooptional: json (default) or markdown (compact, readable)
max_charsNooptional: cap the answer at about this many characters (lists are shortened and marked truncated; use offset/nextOffset to get the rest)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / date / description
      Added value: +"a date as YYYY-MM-DD; gives the portion read on the Shabbat on or after it"
    • addedInput schema / properties / list / description
      Added value: +"true returns every portion"
    • addedInput schema / properties / name / description
      Added value: +"portion name, e.g. Toledot"
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world behavior, so the description's job is to add operational context. It adds meaningful details beyond annotations: the Diaspora calendar convention, the default of returning this week's portion when no input is given, and the exact meaning of the date parameter relative to Shabbat.

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?

The description is two dense sentences that front-load what is returned and then explain accepted inputs and usage context. Every clause carries useful information, though the first sentence is long and could be more scannable.

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?

There is no output schema, so the description carries the return-value burden and does so by listing the returned fields and readings. With all five parameters documented in the schema and usage modes explained in the description, an agent has enough to call it correctly, though markdown formatting and max_chars truncation are left to the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3, but the description adds cross-parameter meaning: no arguments returns this week's portion, a date returns the portion for the Shabbat on or after that date, and list=true returns every portion. It also gives a concrete name example ('Toledot'), reinforcing the name parameter's expected format.

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 states a specific verb and resource ('Returns a weekly Torah portion') and enumerates the returned fields: name, Hebrew name, meaning, Shabbat date, Torah/Haftarah/Besorah readings, and links. It also establishes the calendar scope ('Diaspora calendar'), which distinguishes it from generic passage tools in the sibling list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly says when to use the tool ('when the user asks about a weekly Torah portion, its Haftarah or its New Testament reading') and explains the accepted input modes: name, date, list=true, or none for this week's portion. It stops short of naming alternatives or explicit exclusions, so it earns a 4 rather than a 5.

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.

Resources