Skip to main content
Glama
amranu

DigitalOcean MCP Server

by amranu

get_endpoint_details

Retrieve comprehensive details for a specific DigitalOcean API endpoint using its operation ID, enabling precise API integration and management via the MCP server.

Instructions

Get detailed information about a specific endpoint

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationIdYesOperation ID of the endpoint

Implementation Reference

  • The handler function that implements the core logic of the get_endpoint_details tool. It retrieves the endpoint by operationId using the findEndpoint helper, formats a detailed markdown-like string with method, path, operationId, summary, description, tags, and parameters list, and returns it as text content.
      private async handleGetEndpointDetails(args: any) {
        const { operationId } = args;
        
        const endpoint = findEndpoint(operationId);
        if (!endpoint) {
          throw new Error(`Endpoint not found: ${operationId}`);
        }
    
        const paramsList = endpoint.parameters.length > 0 
          ? endpoint.parameters.map(p => 
              `  • ${p.name} (${p.in}): ${p.type} ${p.required ? '(required)' : '(optional)'} - ${p.description}`
            ).join('\n')
          : '  None';
    
        const details = `
    **${endpoint.method} ${endpoint.path}**
    
    **Operation ID:** ${endpoint.operationId}
    
    **Summary:** ${endpoint.summary}
    
    **Description:** ${endpoint.description}
    
    **Tags:** ${endpoint.tags.join(', ')}
    
    **Parameters:**
    ${paramsList}
        `.trim();
    
        return {
          content: [
            {
              type: 'text',
              text: details,
            },
          ],
        };
      }
  • The input schema defining the parameters for the get_endpoint_details tool, which requires a string 'operationId'.
    inputSchema: {
      type: 'object',
      properties: {
        operationId: {
          type: 'string',
          description: 'Operation ID of the endpoint',
        },
      },
      required: ['operationId'],
    },
  • src/index.ts:114-127 (registration)
    Registration of the get_endpoint_details tool in the ListToolsRequest handler, including name, description, and input schema.
    {
      name: 'get_endpoint_details',
      description: 'Get detailed information about a specific endpoint',
      inputSchema: {
        type: 'object',
        properties: {
          operationId: {
            type: 'string',
            description: 'Operation ID of the endpoint',
          },
        },
        required: ['operationId'],
      },
    } as Tool,
  • src/index.ts:174-175 (registration)
    Dispatch registration in the CallToolRequest switch statement that calls the handler for get_endpoint_details.
    case 'get_endpoint_details':
      return await this.handleGetEndpointDetails(args);
  • Key helper function used by the handler to locate the specific endpoint by its operationId from the cached endpoints list.
    export function findEndpoint(operationId: string): DOEndpoint | undefined {
      const endpoints = loadEndpoints();
      return endpoints.find(ep => ep.operationId === operationId);
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states this is a read operation ('Get'), but doesn't mention potential side effects, authentication requirements, rate limits, error handling, or the format of the returned information. This leaves significant gaps for a tool with no annotation coverage.

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 with zero wasted words. It's front-loaded with the core purpose and appropriately sized for a simple tool, making it highly efficient and easy to parse.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'detailed information' includes, how to handle errors, or any behavioral traits. For a tool with no structured data beyond the input schema, more context is needed to fully guide an agent.

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?

The schema description coverage is 100%, with the parameter 'operationId' fully documented in the schema. The description adds no additional meaning about the parameter beyond implying it identifies a 'specific endpoint', which is already covered by the schema's description. This meets the baseline for high schema coverage.

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 ('Get') and resource ('detailed information about a specific endpoint'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'list_endpoints' or 'search_endpoints' beyond the 'specific' qualifier, which is why it doesn't reach a perfect score.

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'. It mentions 'specific endpoint' but doesn't clarify prerequisites, such as needing an operation ID from another source, or exclusions for when other tools might be more appropriate.

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