Skip to main content
Glama

Keelen

by io.github.jamie7893

resolve_escalation

Idempotent

Acknowledge a handled ask only when no blocked task becomes invisible.

`decision_md` is a required short note (why/how it was resolved), appended to
the escalation's detail_md as an audit trail. Resolving a project_pause /
orphan_pause RESUMES the project (clears the pause). A blocked task's final
task_block/operator_action cannot be acknowledged: use its typed retry,
platform-policy resolution, replan, close, or supersede operation instead.
Idempotent. Accepts a real escalation UUID or a synthetic `orphan:<project_id>`.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
decision_mdYes
escalation_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

TDQS

A5/5.0
Behavior5/5

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

Beyond the annotations, it discloses that decision_md is appended as an audit trail to detail_md, that resolving a project_pause/orphan_pause 'RESUMES the project', and that the tool accepts a synthetic 'orphan:<project_id>' in addition to a UUID. The idempotent claim matches the annotation; no contradiction.

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

Conciseness5/5

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

Five dense sentences, each carrying operational information; the safety condition is front-loaded and the alternative usage is clearly separated. No filler or repetition beyond the single 'Idempotent' marker.

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

Completeness5/5

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

The description covers safety condition, parameter meaning, side effects, idempotency, and alternate routing to sibling tools. With an output schema present and annotations handling destructive/read-only signals, nothing essential is missing for an agent to select and call this correctly.

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

Parameters5/5

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

With 0% schema coverage, the description fully compensates: decision_md is explained as a required short resolution note appended as audit trail, and escalation_id is defined by its accepted formats (real escalation UUID or synthetic orphan:<project_id>). Both required parameters get semantic meaning beyond raw string names.

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

Purpose5/5

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

The description opens with a specific verb and resource ('Acknowledge a handled ask') and adds a precise guarding condition ('only when no blocked task becomes invisible'). It later distinguishes this operation from sibling resolution paths, so an agent can identify what the tool is for.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

It says exactly when to resolve ('only when no blocked task becomes invisible') and when not to: 'A blocked task's final task_block/operator_action cannot be acknowledged.' It explicitly names alternatives ('typed retry, platform-policy resolution, replan, close, or supersede operation'), which maps to sibling tools.

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

All Keelen toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation5/5

Every tool targets a distinct resource and action duo, even within clusters like request handling or security reviews. The get_ vs run_ pairs are clearly separated, and descriptions explicitly contrast confusing alternatives such as archive_project vs delete_project.

Naming Consistency4/5

The set overwhelmingly follows verb_noun snake_case (submit_request, list_projects, resolve_escalation). The one visible deviation is project_status, which breaks the get_/pattern, and signup is a single-word verb instead of sign_up.

Tool Count2/5

37 tools is well above the 25+ threshold and spans auth, billing, project lifecycle, roadmap, escalations, product documents, and multiple review types. Most tools earn their place, but the surface is too large for one server and would be more coherent split into focused servers.

Completeness4/5

The domain coverage is broad: full project lifecycle, request intake/refinement, roadmap manipulation, escalation handling, product doc read/write, and security/legal review flows. Minor gaps exist, most notably no dedicated task-listing or task-update tool, but agents can work around these via project_status and list_escalations.

Resources