Skip to main content
Glama

La Iglesia Católica de los Agentes de AI

Readings of the day

readings_of_the_day
Read-onlyIdempotent

{"use_when":{"en":"Use when someone asks for the Mass readings or the Gospel of a date (Roman Lectionary).","es":"Úsala cuando pregunten por las lecturas o el Evangelio del día."},"what":{"en":"Readings of the day's Mass (first reading, psalm, second reading on Sundays/solemnities, gospel) with full text.","es":"Lecturas del día con su texto."}}

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": "readings_of_the_day"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoDate YYYY-MM-DD. Omit for today in Europe/Berlin; any other value (today, hoy, 2026/11/08, empty) is an error / Fecha AAAA-MM-DD; sin fecha, hoy en Berlín
langNoLanguage / Idioma: es (default), en, ites
bibleNoBible id (e.g. drc, webc, kjv, torresamat, rv1909; see about or /api/bibles). Default: the Catholic Bible of the language if available, else another one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / bible / description
      Previous value: -"Bible id (e.g. drc, kjv, torresamat, rv1909; see about or /api/bibles). Default: the Catholic Bible of the language if available, else another one."New value: +"Bible id (e.g. drc, webc, kjv, torresamat, rv1909; see about or /api/bibles). Default: the Catholic Bible of the language if available, else another one."
  2. Changed1 schema field changed
    • changedInput schema / properties / date / description
      Previous value: -"Date YYYY-MM-DD (default: today in Europe/Berlin) / Fecha (por defecto hoy en Berlín)"New value: +"Date YYYY-MM-DD. Omit for today in Europe/Berlin; any other value (today, hoy, 2026/11/08, empty) is an error / Fecha AAAA-MM-DD; sin fecha, hoy en Berlín"
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral content by disclosing which readings are returned and that a second reading appears only on Sundays/solemnities, plus full text output; it omits any failure or empty-day behavior.

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

Conciseness3/5

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

The use_when/what split is well front-loaded, but the content is a JSON blob embedded as a string and every statement is duplicated in Spanish, roughly doubling length for an agent that reads one language. The information itself is tight with no padding beyond that duplication.

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?

For a zero-required-parameter read tool with full schema coverage but no output schema, the description usefully compensates by enumerating the returned reading components and their Sunday/solemnity conditional. Nothing critical for correct invocation is missing, though the absence of output schema leaves minor uncertainty about the response shape.

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 each of the three parameters (date, lang, bible) already carries a description including the Europe/Berlin default and accepted formats. The description text itself adds no parameter meaning beyond what the schema provides, so the baseline 3 applies.

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 'what' field states a specific resource and scope: the day's Mass readings (first reading, psalm, second reading on Sundays/solemnities, gospel) with full text under the Roman Lectionary. It is clear what is returned, though it never explicitly distinguishes itself from the sibling mass_of_the_day, which an agent must infer from the name alone.

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?

The 'use_when' field gives an explicit trigger: use when someone asks for the Mass readings or the Gospel of a date. That is a clear positive condition with no exclusions or named alternatives, so it falls just short of 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