Skip to main content
Glama

aw.session.open

Create a private15-minute remote processing session. No local installation and no personal input is sent by opening it.

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": "aw.session.open"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare that this is not read-only, not open-world, and not destructive. The description adds meaningfully beyond that: the session is private, it lives 15 minutes, and opening it sends no personal input and requires no local installation. What remains unstated is what a session object contains and what happens at expiry.

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?

Two short sentences, front-loaded with the action and duration, with no filler. The only flaw is a missing space in 'private15-minute', which mildly hurts readability.

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

Completeness3/5

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

For a zero-parameter session-creating tool, the description covers lifetime and privacy but says nothing about what opening returns (presumably a session identifier) or how that handle is used with siblings such as aw.session.close. With no output schema to fill the gap, that omission leaves an agent unsure of next steps.

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

Parameters4/5

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

The tool takes zero parameters, so the schema requires no semantic explanation and the baseline of 4 applies. Nothing in the description contradicts the empty input schema.

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 states a specific verb and resource (create a private 15-minute remote processing session), which is far more informative than the dotted name alone. It does not differentiate from the sibling aw.session.close, but the create/close pairing is self-evident from the verb.

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?

Usage is only implied: 'No local installation and no personal input is sent by opening it' suggests it suits users who want remote processing without installing anything. There is no explicit when-to-use or when-not-to-use statement, and no mention of the need to later close the session.

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