Get escalation policy
get_escalation_policyOne policy by UUID. Reveals step sequence, linked schedules, and contact channels.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| uuid | Yes | Escalation policy UUID (format "esc_..."). |
hyperping
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A3.6/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must disclose behavior. It mentions what is returned but does not state it is a read-only operation, idempotent, or any side effects. Minimal transparency.
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?
The description is a single concise sentence that front-loads the purpose and output details. No wasted words.
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?
Given the simple input schema (one parameter) and no output schema, the description adequately explains what the tool returns. It could mention error handling or uniqueness, but overall sufficient for a get operation.
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?
The input schema has 100% coverage with a description for the uuid parameter. The tool description adds no new semantics beyond the schema, so baseline score 3 is appropriate.
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?
The description clearly states 'One policy by UUID,' indicating a specific retrieval operation. It details what is revealed (step sequence, linked schedules, contact channels), distinguishing it from list_escalation_policies.
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 description implies use when a specific UUID is known, but does not explicitly state when to use versus alternatives like list_escalation_policies. No when-not or context provided.
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.