Skip to main content
Glama

msza.ai — Polish Catholic Sermons ✝

Get a public church profile

get_church
Read-onlyIdempotent

Returns a saved public church profile by camera_id with bounded description, address, stored Mass schedule, website, and update time. Profiles can be AI-enriched and schedules can be outdated. The result reads saved data without profile refresh or generation.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "camera_id": "<camera_id>"
    },
    "name": "get_church"
  }
}

Input Schema

NameRequiredDescriptionDefault
camera_idYesExact public camera_id returned by list_churches.

Output Schema

NameRequiredDescriptionDefault
urlYes
nameYes
addressYes
camera_idYes
updated_atYes
descriptionYes
website_urlYes
mass_scheduleYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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 bar is low. The description adds genuinely useful context beyond them: profiles may be AI-enriched, Mass schedules may be outdated, and the result is a stored snapshot with no refresh or generation triggered.

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?

Three tight sentences: identity first, staleness caveat second, non-mutating behavior third. No filler, and the most decision-relevant facts are front-loaded.

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 single-parameter read with full annotations and an output schema, the description covers what the agent needs: the lookup key, the staleness risk, and the fact that no generation is triggered. Enumerating return fields is slightly redundant against the output schema, but nothing important 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 single camera_id parameter is already documented as an exact public camera_id returned by list_churches. The description's "by camera_id" adds no syntax or format detail beyond the schema, so the baseline of 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 description states a specific verb and resource ("Returns a saved public church profile by camera_id") and enumerates the returned fields, so an agent knows exactly what this fetches. It does not explicitly distinguish itself from the sibling list_churches (that routing only appears in the schema's camera_id description), so it falls short of full sibling differentiation.

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 result reads saved data without profile refresh or generation" implies this is the cheap lookup path, but the description never states when to use this tool versus list_churches or what prerequisites exist. Usage is only inferable, not stated.

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