Escalate Anything

by alexgaoth

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

List follow-ups due

followups_due

Read-only

Lists open cases with a due follow-up date and no activity since, helping you identify overdue follow-ups to act on.

Instructions

Open cases whose follow-up date has come and that had no activity since.

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

Input Schema

Name	Required	Description	Default
`on_or_before`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.2Nov 13, 2026

TDQS

C2.9/5.0

Behavior3/5

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

The annotations already establish read-only and closed-world behavior, so the description's main added value is the selection rule: open cases, follow-up date reached, no activity since. However, 'no activity since' is ambiguous because it does not state the reference point, and the description does not explain default date behavior.

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 definition is a single front-loaded sentence with no wasted wording. The phrase 'that had no activity since' is elliptical and slightly awkward, but the overall structure is efficient.

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?

This is a simple read-only tool with an output schema, so it does not need return-value documentation. Still, for correct invocation an agent needs to understand on_or_before and the meaning of 'no activity since,' both of which are missing from a one-sentence description.

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% for the sole parameter, on_or_before, so the description must compensate. It does not mention the parameter at all, leaving its date format, default null behavior, and whether it overrides the current-date cutoff undocumented; only the general concept of a due follow-up is conveyed.

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 identifies a specific resource set: open cases whose follow-up date has arrived and which have had no activity since. That is clearer than a generic list tool, but it does not distinguish this from siblings such as case_list or list_issues.

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, no mention of alternatives, and no exclusion criteria. An agent can infer that this is for reviewing due follow-ups, but the definition leaves selection entirely to inference.

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