Escalate Anything

Overview Schema Source Related Servers Discussions Admin

Log a contact on a case

case_log

Log case contacts, responses, promises, documents, and escalation rungs, then set follow-up dates to track unresolved complaints.

Instructions

Record what happened on a case. kind: contact, sent, response, promise, reference, document, escalation or note. rung: the escalation rung this contact used (frontline, retention, written_complaint, executive, regulator, state_agency, payment_dispute, ...). Dates are YYYY-MM-DD. Set follow_up_on to the date to check back if nothing happens.

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": {
      "case_id": "<case_id>",
      "kind": "<kind>",
      "text": "<text>"
    },
    "name": "case_log"
  }
}

Input Schema

Name	Required	Description	Default
`kind`	Yes
`rung`	No
`text`	Yes
`case_id`	Yes
`channel`	No
`promised`	No
`rep_name`	No
`reference`	No
`occurred_on`	No
`follow_up_on`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.2Nov 13, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already indicate this is a non-read-only, non-destructive, closed-world mutation. The description adds useful domain context with acceptable kind values, escalation rung examples, and date formatting, but does not explain side effects such as whether logging changes case state or creates follow-up obligations.

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

Conciseness4/5

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

The description is front-loaded with the core action and then provides focused parameter notes. It is reasonably concise for a 10-parameter tool, though the rung examples end with an ellipsis and the formatting is not particularly polished.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 10-parameter mutation tool with no schema descriptions, the definition does not fully document optional fields like channel, promised, rep_name, and reference. Output schema and annotations reduce the burden for return values and safety, but important invocation details remain missing.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry parameter meaning. It explains kind, rung, and follow_up_on reasonably well, and says dates use YYYY-MM-DD, but it leaves channel, promised, rep_name, reference, and the intended content of text under-specified.

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

Purpose4/5

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

The description states a clear verb and resource: 'Record what happened on a case,' which distinguishes it from case_open, case_close, case_get, and case_list. It does not explicitly name siblings, but the logging purpose is clear enough for selection.

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 usage instruction for follow_up_on ('set ... if nothing happens'), but does not explain when to use case_log versus case_close, followups_due, or other related tools. Usage is implied rather than fully guided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.