Skip to main content
Glama
Sign In
umbra

umbra

by lxchx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Session List

session_list

List all saved session blobs and inspect their metadata, including name, domain, save time, and size, without requiring a passphrase.

Instructions

List all saved session blobs (metadata, no passphrase needed).

Ex: session_list() → {"sessions":[{"name":"github-me","domain":"github.com","saved_at":...,"size":1234}]}

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose two genuinely useful traits — results are metadata only and no passphrase is required — plus a concrete response example. However, it never states that the operation is strictly read-only/non-destructive or that it cannot decrypt or modify blobs, which matters in a session-management context.

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 lines: a purpose sentence followed by a concrete example. Front-loaded and free of padding, though the inline response sample partially duplicates the existing output schema.

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?

A parameterless list tool with an output schema needs little prose, and the description supplies the one non-obvious fact (no passphrase required) plus a sample payload. It would be fully complete with an explicit read-only/safe statement.

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?

Zero parameters, so per the baseline this scores 4. The description correctly frames the call as taking no arguments via the 'session_list()' example.

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?

States a specific verb and resource ('List all saved session blobs') plus the key qualifier 'metadata, no passphrase needed', which tells the agent this is an inspection-only listing. It doesn't explicitly name session_load/session_save/session_delete as the alternatives, so differentiation is only implicit.

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 phrase 'no passphrase needed' hints that this is the cheap way to inspect sessions before calling session_load, but the description never states when to use it versus those siblings or any preconditions. The example call implies a read-only inventory step but leaves the routing inference to the agent.

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

Deploy Server

Other Tools