Inbox Triage

End a mutating triage pass (release the lease, stamp activity)

end_triage

Idempotent

Releases the lease begin_triage acquired and records lastTriageEndedAt/lastTriageBy/lastTriageSummary. Call this when a mutating pass finishes (or fails) so the inbox is free for the next agent/pass promptly instead of waiting out the TTL. Idempotent: calling it with no active lease still stamps completion and returns ok:true (note:'no_active_lease') rather than erroring. Pass a short summary (capped 500 chars) describing what happened. It is visible to the human and the next agent via get_triage_activity.

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": {
      "inboxId": "<inboxId>",
      "agentLabel": "<agentLabel>"
    },
    "name": "end_triage"
  }
}

Input Schema

Name	Required	Description
`inboxId`	Yes
`summary`	No	Short human-readable summary of what this pass did, e.g. "archived 12 promos, left 2 VIP emails for review".
`agentLabel`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 26, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the annotations, it discloses concrete behavior: releasing the lease, stamping specific activity fields, idempotent success when no active lease exists, the returned ok:true with note:'no_active_lease', and the summary visibility through get_triage_activity.

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?

The description is four concise sentences, front-loads the core action, and each sentence adds useful operational detail about lease release, idempotency, summary content, and visibility.

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

Completeness4/5

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

For a three-parameter mutation tool with no output schema, it provides enough to call correctly: when to use it, idempotent no-lease behavior, summary constraints, and partial return behavior. The remaining gap is that required inboxId and agentLabel are not explicitly defined.

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 low at 33%, so the description must compensate. It explains the summary parameter well, including the 500-character cap and its visibility via get_triage_activity, and indirectly connects inboxId to freeing the inbox and agentLabel to lastTriageBy, but it does not explicitly define inboxId or agentLabel.

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 states a specific verb and resource: releases the lease acquired by begin_triage and records lastTriageEndedAt/lastTriageBy/lastTriageSummary. It also differentiates this close/cleanup operation from the sibling begin_triage and the activity-reading get_triage_activity.

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

Usage Guidelines4/5

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

It explicitly says to call this when a mutating pass finishes or fails, and explains the consequence of freeing the inbox instead of waiting out the TTL. It does not give explicit when-not-to-use guidance, but the context is otherwise clear.

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

All Inbox Triage tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?