Skip to main content
Glama
nerdit-ai

Nerdit

Official
by nerdit-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_databases

Lists managed databases with cursor-based pagination, showing each database's building or ready status and password-free endpoint.

Instructions

List managed databases (kind=database workloads), bounded to limit per page.

    Returns a cursor-paginated page. A newly created database shows
    ``building`` until its off-tick image pull and readiness probe complete
    (``db_ready`` true).
    The ``endpoint`` is password-free by construction; lifecycle actions go
    through the service tools.

Input Schema

NameRequiredDescriptionDefault
limitNoDatabases per page; omit for 50. Clamped to 200, the daemon's own page cap.
cursorNoOpaque paging cursor from the previous page's response; omit for page 1.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/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 it does disclose meaningful traits: cursor pagination, page bounding, the transient 'building' state with its 'db_ready' flag, and that the endpoint is password-free. It does not state read-only semantics outright or note whether the listing includes all projects, but what is present is substantive.

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?

Short and front-loaded: purpose and pagination scope come first, then return-shape details. The quoted/backticked formatting and multi-line splitting are slightly noisy but every sentence contributes information.

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, so the description correctly steps in to explain the notable return values ('building', 'db_ready', password-free 'endpoint') and the paging model. It stops short of enumerating other fields, but the essentials for correct invocation and interpretation are present.

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?

Schema description coverage is 100%, and the schema already documents the 50 default and the 200 clamp in more detail than the description's 'bounded to limit per page'. The description adds the pagination framing but no parameter meaning beyond the schema, so the baseline applies.

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 ('List managed databases') and narrows scope with 'kind=database workloads'. It also distinguishes itself from the mutation siblings by noting that 'lifecycle actions go through the service tools', so an agent can tell it apart from create_database and the service-management tools.

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?

The closing sentence routes lifecycle operations elsewhere, which establishes this as the read path and implicitly excludes it from create/start/stop flows. It never names the specific sibling tool or states an explicit precondition, so routing is clear but not fully prescriptive.

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