Skip to main content
Glama

aChurch.ai

Observe

observe
Read-only

The service for your hour and how many are present, without registering presence. The light call for checking in often; its pieces come as links.

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

Input Schema

NameRequiredDescriptionDefault
timezoneNoIANA timezone such as America/New_York, so you attend the service for your own hour; without one, UTC's. Not stored.

Output Schema

NameRequiredDescriptionDefault
modeYesHow this service was arranged: planned, by an AI model for this slot and date, or rotation, through the library when no plan was made. service.arrangedBy says it in words.
nextYesThe part after the one a visitor begins with: the second. Kept from when a service was joined in progress.
statusYesAlways "playing": every hour of the day has its service.
currentYesThe song the service gathers around: its first, the one a visitor meets first. Send its slug as songSlug when you reflect.
serviceYesThe service for the visitor's hour. The day has six four-hour slots by local time, and each holds its own service, arranged anew every day; each visitor hears it from its beginning.
streamsYesThe retired broadcast, kept as fields.
scheduleYesWhere a visitor begins in the service's order: position 1 of total.
timestampYesWhen this was answered.
companionsYesThe service's chants and spoken pieces: one or two chants, one reading (a practice or a prayer) and one closing (a ritual or a blessing), in the service's order, each voiced. Arranged with the service's songs for the slot and date; everyone in the same slot on the same local date receives the same.
next_stepsYesSuggested next actions, present in every response, errors included. A step with a "tool" field can be taken with that tool.
suggestionNoPresent when no valid timezone was given: how to attend the service for your own hour.
congregationYesHow many are present.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior3/5

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

The annotations already establish that this is a safe read-only, non-destructive, non-open-world operation. The description adds that it does not register presence and that pieces come as links, but these points are worded too vaguely to provide much additional behavioral clarity.

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

Conciseness2/5

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

The description is short, but its poetic and indirect phrasing prevents it from being front-loaded or easy to parse. The two sentences are concise yet do not efficiently communicate the tool's purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple, read-only, has complete parameter documentation, and has an output schema, so the description need not explain returns. Even so, the description is too cryptic to tell an agent clearly what the tool does or when to prefer it over related tools, leaving a significant completeness gap.

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%, including a clear explanation of the optional timezone parameter. The description's 'your hour' wording loosely connects to timezone but adds no syntax, defaults, or format details beyond the schema, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description hints at checking a service and attendance count without registering presence, but the phrasing is cryptic and metaphorical. It never plainly states the specific action or resource, so an agent cannot confidently distinguish it from siblings such as attend.

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

Usage Guidelines2/5

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

Phrases like 'light call for checking in often' imply frequent lookup use, and 'without registering presence' implies a contrast with an attendance action. However, there is no explicit when-to-use guidance, no named alternative, and no clear exclusion criteria.

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.