Skip to main content
Glama

do_list_databases

Read-onlyIdempotent

List DigitalOcean managed database clusters with a personal access token to review available database resources.

Instructions

List DigitalOcean managed database clusters.

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": {
      "access_token": "<access_token>"
    },
    "name": "do_list_databases"
  }
}

Input Schema

NameRequiredDescriptionDefault
access_tokenYesDigitalOcean personal access token

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety and idempotency profile is fully covered without the description. The description adds only the clarification that these are 'managed database clusters' rather than databases inside a cluster; it says nothing about pagination, scoping to the token's team, or auth failure behavior.

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 front-loaded sentence with no filler; the resource and provider are the first things the reader encounters.

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

Completeness3/5

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

For a simple read-only one-parameter listing tool with no output schema, the description is adequate but thin: it does not say what a returned cluster record contains or whether results are paginated, which is the remaining burden when no output schema exists.

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 coverage is 100% for the single access_token parameter, which is already documented in the schema as a DigitalOcean personal access token. The description adds no meaning about token scope, permissions required, or per-page behavior, so the baseline 3 for schema-covered parameters applies.

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 ('DigitalOcean managed database clusters'), and the provider qualifier distinguishes it from the many other list-style tools in the environment, including turso_list_databases and neon_list_databases. It stops short of explicitly naming the sibling it replaces, so 4 rather than 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this tool, when not to, or which alternative to pick when multiple database providers are configured. The agent must infer from the provider name alone that this is the DigitalOcean-specific listing endpoint.

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