Skip to main content
Glama

Create an escalation policy

create_escalation_policy

Business plans: ordered steps, each alerting contacts and whoever is on call in schedules, then waiting for an acknowledgement before the next. Monitors use it with update_monitor's escalation_policy_id. Free.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "steps": "<steps>"
    },
    "name": "create_escalation_policy"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe policy's name.
stepsYesIn order; sending steps replaces them all. Each names contacts, schedules or both.
repeat_countNoTimes the whole policy runs again when nobody acknowledges.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / name / description
      Added value: +"The policy's name."
  2. First observed

TDQS

B3/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 non-destructive write operation that is not idempotent and not open-world. The description adds useful domain semantics about ordered alert steps and acknowledgement waits, but much of this is also present in the schema and it does not disclose the return value or broader side effects of creation.

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?

The description is short and mostly front-loaded, but the opening fragment 'Business plans:' and the isolated 'Free.' are ambiguous and read awkwardly. It avoids verbosity, yet the structure could be clearer and more directly action-oriented.

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 creation tool with three parameters and no output schema, the description covers the policy concept and a monitor-integration workflow hint. It is still incomplete because it never states the creation action explicitly, does not describe the created result, and leaves the 'Business plans'/'Free' phrasing unexplained.

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%, so the schema already documents all three parameters thoroughly, including nested step fields. The description adds conceptual context but no parameter-specific syntax or constraints beyond what the schema provides, making the baseline 3 appropriate.

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 description explains what an escalation policy consists of (ordered steps, contacts, schedules, acknowledgement waits) but never explicitly states that this tool creates one; the action is only inferable from the name and title. It does not clearly distinguish this tool from update_escalation_policy or delete_escalation_policy.

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?

It gives one useful workflow hint: monitors use the created policy with update_monitor's escalation_policy_id. However, it does not say when to use this versus update_escalation_policy or list preconditions, so guidance remains implied rather than explicit.

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