Get on-call schedule
get_on_call_scheduleOne schedule by UUID with full rotation detail and the linked escalation policies.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| uuid | Yes | Schedule UUID (format "sch_..."). |
hyperping
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A3.5/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided; description only mentions return content but lacks disclosure on error handling, idempotency, or side effects. For a simple read operation, this is minimal.
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?
Single sentence of 12 words, front-loads the core purpose with no extraneous information.
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?
For a simple get-by-ID tool with one parameter, the description covers the return content (rotation detail, escalation policies) but lacks details on response format or potential errors.
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% with a clear description for uuid. The tool description adds no additional meaning beyond restating that it retrieves by UUID.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states it retrieves one schedule by UUID with full rotation detail and linked escalation policies, distinguishing from list_on_call_schedules and other siblings.
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?
Implies usage when you have a UUID and need detailed data, but no explicit when-not-to-use or alternatives like list_on_call_schedules are mentioned.
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.
TDQS
A3.5/5.0
Disambiguation5/5
Each tool targets a specific resource or action (monitor, outage, escalation policy, etc.) with clear naming. No two tools could be easily confused; even similar ones like get_monitor_outages and get_monitor_anomalies serve distinct purposes.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern (create_, get_, list_, pause_, resume_, search_, update_) and use snake_case uniformly. This makes the tool set predictable and easy to navigate.
Tool Count4/5
With 26 tools, the set is slightly above the typical well-scoped range of 3-15, but each tool serves a distinct monitoring function (monitors, outages, escalations, integrations, schedules, alerts, team members). The count is reasonable for the domain.
Completeness2/5
The tool surface is heavily read-oriented, lacking create/update/delete for most resource types (escalation policies, integrations, on-call schedules, outages). Even monitors lack a delete tool. This leaves significant gaps for administrative workflows.