Skip to main content
Glama
platypus-db

platypus-db

Official

list_schemas

List schemas or databases available on a saved connection, showing the current schema for unqualified names and system schemas.

Instructions

Lists the schemas of a connection (databases in MySQL and MariaDB, main and attached databases in SQLite), with current for the one unqualified names resolve to and system for catalog schemas.

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

Input Schema

NameRequiredDescriptionDefault
connectionYesThe connection's name, as `list_connections` shows it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.2

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden; 'Lists' implies a safe read, but this is never stated. It does disclose meaningful output semantics — that the result marks `current` for the schema unqualified names resolve to and `system` for catalog schemas — but says nothing about ordering, pagination, or behavior for an invalid connection name.

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?

A single tight sentence, front-loaded with the verb and resource, with the engine-specific parentheticals and the `current`/`system` clarification each adding distinct value. No filler or restatement of the name.

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 one-parameter read tool with no output schema and no annotations, the description covers what is returned and how to interpret the flags, which is the important gap. Missing only edge-case behavior (invalid connection, empty results) and sibling routing to keep it from a 5.

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

Parameters3/5

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

There is exactly one parameter with 100% schema description coverage, and the schema already says the connection is named as `list_connections` shows it, so the description adds no new parameter meaning. Baseline 3 applies when the schema does all the work.

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 ('Lists the schemas of a connection') and clarifies what a 'schema' means per engine (MySQL/MariaDB databases, SQLite main and attached databases). That makes the resource unambiguous, but it never contrasts itself with siblings such as list_objects or describe_table, so routing relies on the agent's own inference.

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: the reference to 'the connection's name, as list_connections shows it' hints at a follow-on from list_connections, and the engine-specific parenthetical implies when the tool applies. There is no explicit when-to-use, when-not-to-use, or pointer to a sibling for listing tables/objects.

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