Skip to main content
Glama

desktop_session_gc

Remove ended or provably stale desktop sessions, optionally filtering by ended status or age, to keep session records clean and current.

Instructions

agent-desktop session gc: Remove ended or provably-stale sessions

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

Input Schema

NameRequiredDescriptionDefault
endedNoOnly consider sessions that already have ended_at set, and remove them even when their trace was written in the last few minutes
older_thanNoOnly remove sessions whose ended_at/created_at age exceeds this many seconds

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It correctly signals a destructive removal and gives a rough safety criterion ('provably-stale'), but it does not say whether deletion is irreversible, whether associated traces/artifacts are also removed, or whether the call is idempotent. That leaves meaningful gaps for a destructive operation.

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?

A single short clause with the action front-loaded and no filler. Slight deduction because the 'agent-desktop ... gc' phrasing is jargon-heavy and the terseness borders on under-specification rather than true conciseness.

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 destructive maintenance tool with zero annotations and no output schema, yet the description says nothing about what is destroyed, whether traces survive, or what the result reports. For a tool whose whole purpose is deletion, the definition is too thin for an agent to act on safely.

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%, so both parameters are fully documented in the schema itself. The phrase 'ended or provably-stale' loosely maps to the ended/older_than filters but adds no syntax or interaction detail beyond the schema, so the baseline 3 applies.

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 gives a specific verb and resource ('Remove ... sessions') plus a scope qualifier ('ended or provably-stale'), so the agent knows exactly what the tool does. It does not explicitly contrast itself with the sibling desktop_session_end, which ends a live session, so the boundary between ending and garbage-collecting must be inferred.

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?

'ended or provably-stale' implies the condition for calling it, and the parameter descriptions reinforce the two selection criteria. However, there is no explicit statement of when not to use it or which sibling (e.g. desktop_session_end) to prefer for ending a session, so usage is only implied.

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