Skip to main content
Glama
platypus-db

platypus-db

Official

list_connections

Lists saved database connections available to agents with name, ID, driver, type, database, and access level, so they can select the right connection without exposing hosts or credentials.

Instructions

Lists the database connections saved in PlatypusDB that agents may use: name, id, driver, type (dev, test, prod), database and agent_access (read_only or read_write). Never shows hosts, users or passwords.

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_connections"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.2

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does well: it discloses the agent_access values (read_only or read_write) and explicitly states that hosts, users and passwords are never exposed, which is exactly the kind of security context an agent needs. It does not say whether results are permission-filtered or ordered, leaving some behavioral gaps.

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?

Two short sentences, zero filler. The core purpose is front-loaded and the security constraint follows as a tightly scoped second sentence.

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?

There is no output schema, and the description compensates by enumerating the fields returned, including the security exclusion. For a zero-parameter list tool this is nearly complete; only filtering/ordering behavior is unstated.

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 baseline is 4. The description instead documents the returned fields, which is added value rather than redundant schema information.

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?

States a specific verb and resource ("Lists the database connections saved in PlatypusDB") and immediately scopes it to those agents may use. The enumerated fields (name, id, driver, type, database, agent_access) make it unmistakable against siblings like list_objects or list_schemas.

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 "that agents may use" implies the tool is for discovering usable connections, which is useful context. However, there is no explicit when-to-use vs when-not guidance and no reference to any alternative or follow-up tool.

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