Skip to main content
Glama

Messe Oggi

cerca_celebrazioni

Read-onlyIdempotent

Consulta gli orari delle celebrazioni di Messe Oggi per una data (oggi e i prossimi sette giorni, Europe/Rome). Fornisci in risposta la fonte ufficiale, il link dell’evento e il fuso. Un appuntamento in programma non equivale a una diretta verificata.

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

Input Schema

NameRequiredDescriptionDefault
cityNo
dateNo
kindNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: the Europe/Rome timezone, the seven-day forward window, the requirement to surface an official source and event link, and the caveat that a scheduled entry is not a verified live stream.

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?

Three compact sentences, front-loaded with the lookup action and the date window. The closing caveat about scheduled vs. verified live is the only sentence that could be questioned, but it adds real data-quality value rather than padding.

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?

Given no output schema, the instruction to return the official source, event link and timezone usefully describes the response shape, which is a real strength. But with three parameters at 0% schema coverage and no explanation of city or kind, the definition is not complete enough for reliable invocation.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry parameter meaning, yet it only addresses the 'date' parameter (valid window of today through seven days ahead). The 'city' parameter and the 'kind' enum (mass, angelus, rosary, vespers, adoration) are never mentioned or explained, leaving two of three parameters fully undocumented.

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 pairs a specific verb ('Consulta gli orari') with a specific resource ('celebrazioni di Messe Oggi'), so an agent immediately knows this returns scheduled celebration times. It also names the scope (a date within today + next seven days), though it never distinguishes itself from the sibling consulta_contenuti.

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 implicit use case is clear (look up celebration times for a given date), and the 'oggi e i prossimi sette giorni' window implicitly tells the agent when this tool is valid versus out of range. However, there is no explicit when-to-use/when-not-to-use statement and no routing to an alternative tool.

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