Skip to main content
Glama
Sign In
The OtterStax MCP Server

The OtterStax MCP Server

Official
by otterstax
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_schemas

Lists schemas within a database to reveal its structure. Provide a database name to see schema names for MySQL, ClickHouse, or PostgreSQL connections.

Instructions

List the schemas inside a database: '' for a MySQL/ClickHouse connection, '.' for a PostgreSQL one. A local database has none.

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": {
      "database": "<database>"
    },
    "name": "list_schemas"
  }
}

Input Schema

NameRequiredDescriptionDefault
databaseYesDatabase name from list_databases

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that local databases return no schemas and that result naming differs by engine, but says nothing about permissions, pagination, or return shape.

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?

One tight sentence that front-loads the action and immediately follows with the engine-specific convention and the empty-result case. No filler.

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 simple, annotation-free read tool with a single documented parameter and no output schema, the description supplies the key nuances (engine-dependent naming, empty case for local DBs). It is nearly complete, lacking only error/permission behavior.

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% and the single parameter is well documented as coming from list_databases. The description adds real value beyond the schema by explaining the '<db>' vs '<db>.<schema>' input convention depending on the connection type.

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 (List) and resource (schemas inside a database), and the format hints ('<db>' vs '<db>.<schema>') clarify what a schema means per engine. It does not explicitly differentiate itself from siblings like list_tables or list_databases, but the resource is unambiguous.

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 through the naming-format parenthetical and the 'A local database has none' note. There is no explicit when-to-use vs list_databases/list_tables guidance, nor any statement about prerequisites beyond the required 'database' parameter.

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