Skip to main content
Glama

Change an escalation policy

update_escalation_policy
Idempotent

Business plans. Fields left out keep their value; steps replaces them all. 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": {
      "policy_id": "<policy_id>"
    },
    "name": "update_escalation_policy"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoThe policy's name.
stepsNoIn order; sending steps replaces them all. Each names contacts, schedules or both.
policy_idYesPolicy ID from list_escalation_policies.
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

C2.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false. The description adds genuinely useful patch semantics that annotations cannot express: omitted fields are preserved, and "steps replaces them all" warns that sending steps wipes existing steps — a real data-loss footgun. However, the cryptic "Business plans. ... Free." fragments are ambiguous (plan requirement? no charge?) and are not explained, so the added context is valuable but partially unintelligible.

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

Conciseness2/5

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

It is short, but brevity here costs clarity: three sentence fragments with no subject or verb, and the plan/free fragments are unparseable without outside knowledge. The genuinely useful patch semantics are present but buried rather than front-loaded, so the terseness reads as under-specification rather than economy.

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 4-parameter mutation with full schema coverage and safety annotations, the description covers the mutation mode and the steps-replacement hazard but omits plan/prerequisite details behind "Business plans.", any note on auth or scope, and any differentiation from the create/delete/list siblings. Adequate on patch behavior, incomplete elsewhere.

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%, including per-field notes such as "sending steps replaces them all" and "Policy ID from list_escalation_policies." The description's only parameter-relevant statements restate the preserve-on-omit and steps-replacement semantics already documented in the schema, so it adds little new meaning beyond the structured fields. Baseline 3 is appropriate.

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

Purpose2/5

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

The description never states a verb or resource — the only content is fragmentary clauses ("Business plans.", "Free.") that read as plan-tier footnotes rather than a statement of what the tool does. A reader must fall back on the title and the tool name to learn this updates an escalation policy, and nothing distinguishes it from create_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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance and no named alternative. "Business plans." hints at a plan/entitlement prerequisite and "Fields left out keep their value" implies a partial-update mode, but neither is stated as actionable guidance for choosing this tool over a create/delete sibling.

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