Skip to main content
Glama
platypus-db

platypus-db

Official

list_open_sessions

List open PlatypusDB sessions to see what the user is working on, including each session's connection, database, purpose, manual-commit mode, and open transaction status.

Instructions

Lists the sessions open in the PlatypusDB app, when it is open: their connection, the database when it is not the connection's own, purpose (main for the session the connection's editor tabs and navigator share, side for one a dialog opened), whether it runs in manual-commit mode and whether a transaction is open in it. Your statements run on sessions of your own, never on these: use it to know what the user is working on.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.2

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses the precondition (only meaningful when the app is open), clarifies these sessions are not the agent's own, and explains the meaning of the `main` vs `side` purpose values. It omits error behavior when the app is closed and does not explicitly confirm the operation is non-mutating, leaving a modest gap.

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?

Key information is front-loaded with the verb and resource first, and every clause adds content about returned fields rather than padding. The single long sentence with nested parentheticals ("the database when it is not the connection's own") is slightly dense but not wasteful.

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 zero-parameter read tool with no annotations and no output schema, the description adequately describes the return shape, the app-open precondition, and the relationship to the agent's own sessions. It could go one step further by stating what happens when the app is closed (empty list vs error).

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 baseline is 4 by rule. The description correctly implies a no-argument call and adds meaning about what the result set contains rather than leaving it opaque.

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?

Names a specific verb and resource ("Lists the sessions open in the PlatypusDB app") and enumerates the fields returned: connection, database, purpose (main/side), manual-commit mode, and open transaction. It also draws a sharp boundary against the agent's own sessions, so an agent can tell this apart from query-execution tools without opening any schema.

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?

"use it to know what the user is working on" gives clear positive guidance, and "Your statements run on sessions of your own, never on these" prevents the common misuse of assuming these are the agent's sessions. It stops short of naming an explicit alternative or exclusion case, so it is not a full when/when-not statement.

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