Skip to main content
Glama
platypus-db

platypus-db

Official

server_activity

Inspect live database sessions, running statements, waits, blocking sessions, and locks to diagnose contention; read-only and prioritized by waiting or long-running work.

Instructions

What the database server is doing now: its sessions (user, database, client, state, the statement running and for how long, what it waits for and the sessions blocking it) and the locks held or waited for, as in the PlatypusDB admin tab; sessions that wait or run first, 50 by default (limit, up to 200). The statements are other people's: credentials and the values of sensitive columns are masked, and long ones cut at 500 characters. PostgreSQL, MySQL, MariaDB and SQL Server; read-only: nothing is cancelled or ended. A missing privilege is said so.

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": {
      "connection": "<connection>"
    },
    "name": "server_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoEntries returned at most: sessions for `server_activity` (50 by default, up to 200), statements for `top_queries` (20 by default, up to 100).
connectionYesThe connection's name, as `list_connections` shows it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.2

TDQS

A4.1/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so: it declares read-only behavior ('nothing is cancelled or ended'), discloses masking of credentials and sensitive column values, truncation of long statements at 500 characters, surface-level reporting of missing privileges, and supported engines. These are exactly the operational traits an agent needs before calling.

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?

The single paragraph is front-loaded with the resource and its contents, then safety/privacy, then engine coverage. The long parenthetical enumeration of session fields is dense but earns its place. Slightly heavy for one sentence, but no filler.

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

Completeness5/5

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

No output schema and no annotations exist, yet the description enumerates the returned fields, ordering, default and maximum result size, masking and truncation rules, supported database engines, read-only safety, and error reporting. Nothing material an agent needs in order to call this correctly is missing.

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?

Schema coverage is 100%, so the limit default and ceiling are already documented. The description still adds value by stating which sessions are returned first ('sessions that wait or run first'), clarifying what the limit actually selects, and by tying connection context implicitly to the admin-tab view.

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 resource and scope: live sessions (user, database, client, state, running statement, wait events, blockers) plus locks held or waited for. An agent knows exactly what comes back. It does not distinguish itself from the sibling list_open_sessions, so it stops short of a 5.

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 by 'what the database server is doing now' and the reference to the PlatypusDB admin tab, which signal live diagnostics. There is no explicit when-to-use versus list_open_sessions, top_queries, or search_history, and no when-not-to-use guidance.

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