Skip to main content
Glama

Escalation policies

list_escalation_policies
Read-only

Business plans: escalation policies, whose id a monitor's escalation_policy_id takes, and their steps. Free.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds only that returned policies carry steps and that the id is what a monitor's escalation_policy_id references; it says nothing about ordering, pagination, or what the plan/free wording actually constrains, which reads ambiguously.

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

Conciseness3/5

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

It is short, but it is a sentence fragment with no verb and an unexplained trailing 'Free.', so brevity comes at the cost of parseability. A single clear sentence stating 'lists escalation policies and their steps' would be both shorter and clearer.

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 parameterless read tool with no output schema, the description covers the resource, the nested steps, and the monitor linkage, which is roughly adequate. It still omits result ordering/shape and leaves the plan-gating claim ambiguous, so it is minimally sufficient rather than complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no schema semantics for the description to compensate for; the baseline for a no-param tool applies. The description correctly implies no filtering arguments are needed.

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

Purpose3/5

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

The fragment names the resource (escalation policies plus their steps) and ties it to monitors via escalation_policy_id, but there is no verb and the leading 'Business plans:' / trailing 'Free.' phrases muddy rather than clarify what the call does. An agent must lean on the tool name 'list_' to infer that this is a read/list operation.

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?

'Business plans:' hints at a plan prerequisite, but that is a constraint, not usage guidance. Nothing says when to call this versus list_monitors, get_monitor, or the create/update/delete escalation-policy siblings, and there are no exclusions or sequencing hints.

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