Skip to main content
Glama

Who is on call

oncall_lookup
Read-onlyIdempotent

Retrieve primary, secondary, and escalation on-call contacts for a team at a specified time, defaulting to now. Use it to find the right person during incidents or handoffs.

Instructions

Primary, secondary and escalation contacts for a team’s on-call rotation at a given time (default: now). Rotations hand off Mondays 09:00 Central. Requires role: viewer.

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

Input Schema

NameRequiredDescriptionDefault
atNoISO 8601 time; default now
teamNoOmit for all teams

Output Schema

NameRequiredDescriptionDefault
atYes
shiftsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the bar is lower, yet the description still adds two things structured data cannot convey: the rotation cadence ('hand off Mondays 09:00 Central'), which tells an agent that results change discontinuously and that timezone matters, and an authorization prerequisite ('Requires role: viewer'). What it omits is failure behavior — whether a missing rotation returns empty contacts or an error — which keeps it off a 5.

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 short sentences, each carrying a distinct payload: what is returned, how the rotation behaves over time, and the auth gate. The highest-value constraint (the default time and the handoff schedule) is placed early rather than buried, 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?

An output schema exists, so return values need not be explained, and both parameters are fully documented in schema. Against that, the description supplies the missing operational context — cadence and required role — making it callable without follow-up questions. The only residual gap is edge-case outcome (empty rotation, all-teams aggregation across differing cadences).

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 coverage is 100%: both `at` (ISO 8601, default now) and `team` (enum, omit for all teams) are fully documented in the schema, so baseline 3 applies. The description's re-statement of the 'now' default and 'a team's' framing adds no syntax, format, or enum semantics beyond what the schema already gives.

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 names the exact resource (a team's on-call rotation) and, more usefully, the shape of the answer: primary, secondary and escalation contacts at a given time. That is far more specific than a title restatement. It stops short of explicit sibling differentiation, but no sibling in the list covers on-call contacts, so the resource name alone disambiguates.

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?

Usage is implied rather than stated: the 'default: now' parenthetical signals this is for current or point-in-time lookups, and the handoff note implies answers are step functions in time. There is no explicit guidance on when to prefer this over other lookups, nor any exclusion such as historical windows before a rotation change or behavior when a team has no rotation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.