Skip to main content
Glama

La Iglesia Católica de los Agentes de AI

Saint of the day

saint_of_the_day
Read-onlyIdempotent

{"use_when":{"en":"Use when someone asks which saint is remembered today or on a date.","es":"Úsala cuando pregunten qué santo se recuerda hoy o en una fecha."},"what":{"en":"Commemoration of the day from the project's list of saints (rank, grc, short note, example for agents). It is NOT the liturgical celebration that governs the day: for that use liturgical_calendar (celebration) or mass_of_the_day. rank = the saint's rank (solemnity, feast, memorial, optional_memorial, traditional = not in the General Roman Calendar, kept by tradition); grc = true if the saint is in the General Roman Calendar.","es":"Conmemoración del día según la lista de santos del proyecto (rank, grc, nota y ejemplo para agentes). No es la celebración litúrgica que rige el día: esa está en liturgical_calendar o mass_of_the_day."}}

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": "saint_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

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds domain behavior the annotations cannot convey: the meaning of rank values (solemnity through traditional) and that grc flags General Roman Calendar membership. It does not restate return shape beyond field names, which is a minor gap.

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 bilingual JSON is front-loaded with use_when before what, and each clause carries information (scope, exclusions, field definitions). It is somewhat repetitive because every string is duplicated in Spanish and English, and the parenthetical "example for agents" is vague, but there is no filler prose.

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 two-optional-parameter read tool with no output schema, the description covers purpose, exclusions, and the meaning of the non-obvious return fields, which is what an agent needs to call and interpret it. It could say more about the response envelope, but nothing essential to correct invocation is missing.

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% and the schema already documents the YYYY-MM-DD pattern, the Europe/Berlin default, and the es/en/it language enum with default es. The description adds no parameter-level detail beyond that, so the baseline 3 applies.

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 "what" field states a specific verb+resource: it returns the day's commemoration from the project's saint list, and enumerates the returned fields (rank, grc, short note). It explicitly distinguishes itself from siblings by saying it is NOT the liturgical celebration and naming liturgical_calendar and mass_of_the_day instead.

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

Usage Guidelines5/5

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

A dedicated "use_when" field gives the triggering question ("which saint is remembered today or on a date"), and the "what" field adds an explicit exclusion plus the two alternatives to use instead. Both the when and the when-not are stated outright.

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