Skip to main content
Glama
amranu

DigitalOcean MCP Server

by amranu

list_tags

Retrieve all available endpoint tags for DigitalOcean API to improve search, filtering, and targeted API calls.

Instructions

List all available endpoint tags

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Implements the core logic for the 'list_tags' tool: retrieves all unique endpoint tags using getAllTags() and formats them into a textual response.
    private async handleListTags() {
      const tags = getAllTags();
    
      return {
        content: [
          {
            type: 'text',
            text: `Available tags:\n\n${tags.map(tag => `• ${tag}`).join('\n')}`,
          },
        ],
      };
    }
  • src/index.ts:147-155 (registration)
    Registers the 'list_tags' tool in the MCP server's tool list, specifying its name, description, and input schema (no required parameters).
    {
      name: 'list_tags',
      description: 'List all available endpoint tags',
      inputSchema: {
        type: 'object',
        properties: {},
        required: [],
      },
    } as Tool,
  • Defines the input schema for 'list_tags', which accepts an empty object with no required properties.
    inputSchema: {
      type: 'object',
      properties: {},
      required: [],
    },
  • Helper function that loads all endpoints and returns a sorted list of unique tags extracted from them.
    export function getAllTags(): string[] {
      const endpoints = loadEndpoints();
      const tags = new Set<string>();
      endpoints.forEach(ep => ep.tags.forEach(tag => tags.add(tag)));
      return Array.from(tags).sort();
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but only states what the tool does without any behavioral context. It doesn't mention whether this is a read-only operation, what format the results come in, if there are rate limits, or any other behavioral characteristics.

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, clear sentence that gets straight to the point with no wasted words. It's perfectly sized for a simple tool with no parameters.

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 zero-parameter tool with no output schema, the description provides the basic purpose but lacks important context about what 'endpoint tags' are, how they relate to endpoints, and what the output format looks like. The absence of annotations means more behavioral context should be provided.

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?

The tool has zero parameters, so there's no need for parameter documentation. The description appropriately focuses on the tool's purpose rather than parameter details, which is sufficient given the empty input schema.

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?

The description clearly states the verb ('List') and resource ('endpoint tags'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling 'list_endpoints' or explain what 'endpoint tags' are versus 'endpoints' themselves.

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?

The description provides no guidance on when to use this tool versus alternatives like 'list_endpoints' or 'search_endpoints'. There's no mention of prerequisites, context, or specific use cases for retrieving tags rather than endpoints.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/amranu/digitalocean-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server