Skip to main content
Glama

do_list_droplets

Read-onlyIdempotent

Lists DigitalOcean droplets and flags any that are powered off. Filter by tag or limit results to monitor server status.

Instructions

List DigitalOcean droplets (signals when any are powered off).

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

Input Schema

NameRequiredDescriptionDefault
limitNoDroplets to return (max 200, default 25)
tag_nameNoFilter droplets by tag
access_tokenYesDigitalOcean personal access token

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

A3.8/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 profile is covered. The description adds that results 'signal when any are powered off,' which is useful behavioral context, but it does not elaborate on output format, pagination, or rate-limit 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?

The description is a single front-loaded sentence with no wasted material. The primary operation is stated first, and the parenthetical adds a useful signal without distracting from the main purpose.

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 read-only listing tool, the description plus rich annotations and fully documented schema provide nearly everything an agent needs to invoke it correctly. The only minor gap is that it does not describe the response shape in more detail, though no output schema exists and the mention of powered-off signaling partially compensates.

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%, so the parameters limit, tag_name, and access_token are already fully documented in the schema. The description does not add parameter-specific meaning beyond what the structured schema provides, so the baseline score of 3 is appropriate.

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?

The description uses a specific verb and resource: 'List DigitalOcean droplets.' It clearly distinguishes the tool from nearby siblings such as do_account, do_list_databases, and do_list_apps, and adds a useful behavioral note that results signal powered-off droplets.

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 usage context is implied by the name and description: use this to enumerate DigitalOcean droplets. However, it does not explicitly state when to use this versus related tools like do_account or do_list_apps, nor does it mention prerequisites beyond the access_token already documented in the schema.

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