Skip to main content
Glama

Messe Oggi

consulta_contenuti

Read-onlyIdempotent

Consulta i contenuti pubblici di Messe Oggi. Scegli topic: places (luoghi di culto), broadcasters (emittenti), articles (approfondimenti), readings (letture e Vangelo), saints (santi del giorno), prayers (testi della Liturgia delle Ore), rosaries (programmi del Rosario). Usa slug per un contenuto specifico, query per cercarlo, page per passare alla pagina successiva o date per i contenuti giornalieri. Cita i link ufficiali.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive behavior. The description adds that only public content is returned, explains pagination with page, and instructs citation of official links, though it omits auth, rate-limit, and error behavior.

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 front-loaded with purpose, then moves directly into topic options and parameter usage, ending with a citation instruction. Every sentence carries useful information and there is no filler.

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 multi-branch oneOf tool with no output schema, the description covers the main selection modes and topic vocabulary well. It could clarify that some parameters are valid only for certain topic groups and generally describe returned content, but the schema and annotations fill most remaining gaps.

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 coverage is 100%, so structural constraints are already documented. The description adds meaning by translating each topic enum into its content category and explaining the intended use of slug, query, page, and date.

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 opens with a specific verb and resource ('Consulta i contenuti pubblici di Messe Oggi') and enumerates the exact topic categories available. It does not explicitly contrast with sibling cerca_celebrazioni, but the resource and topic scope are clear enough to identify the tool.

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 gives concrete routing: choose topic, use slug for a specific item, query for search, page for pagination, and date for daily content. It does not state when not to use it or name alternatives such as cerca_celebrazioni.

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