Skip to main content
Glama

aw.session.close

Destructive

Explicitly revoke this transient remote session and remove its remote copies; original disk files are never touched.

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": {
      "session": "<session>"
    },
    "name": "aw.session.close"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionYesPrivate short-lived session capability returned by aw.session.open. Never publish or log it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, so the description's real contribution is bounding the blast radius: remote copies are removed while 'original disk files are never touched'. That directly informs an agent's go/no-go decision on a destructive call. It omits idempotency behavior (what happens if the session is already closed) and any error responses.

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?

One sentence, front-loaded with the action, then the destructive scope, then the safety carve-out. No filler or repetition.

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 one-parameter destructive tool with annotations covering the safety profile, the description supplies the one thing the structured fields cannot: what is destroyed versus preserved. Idempotency and post-close session state remain unstated, which is the only meaningful gap.

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 coverage is 100% and the single parameter already carries a strong description (capability string, never log or publish). The tool description adds nothing about the session argument, so 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?

Specific verb+resource: 'revoke this transient remote session'. The clause about remote copies vs untouched disk files sharpens the scope considerably. It stops short of naming aw.session.open as the counterpart, so an agent must infer the open/close pairing from context.

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?

The word 'Explicitly' hints that closure is normally handled implicitly and this tool is for deliberate teardown, but that is inference rather than stated guidance. No when-not-to-use condition or alternative (e.g., leaving the session to expire) is given.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources