Skip to main content
Glama

get_protocol

Retrieve detailed information about Voi ecosystem protocols by ID to understand contract roles, services, and functionality for protocols like HumbleSwap and Nautilus.

Instructions

Get detailed information about a specific Voi ecosystem protocol by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
protocolIdYesProtocol identifier (e.g. humble-swap, envoi, aramid-bridge)

Implementation Reference

  • The handler function for 'get_protocol' tool. Takes a protocolId parameter, looks up the protocol using findProtocol(), and returns either the protocol details or an error if not found.
    async ({ protocolId }) => {
      const protocol = findProtocol(protocolId);
      if (!protocol) {
        return toolError(`Unknown protocol: ${protocolId}`);
      }
      return toolResult(protocol);
    },
  • Zod schema definition for 'get_protocol' tool input. Defines 'protocolId' as a required string parameter with a description for the protocol identifier.
    {
      protocolId: z
        .string()
        .describe("Protocol identifier (e.g. humble-swap, envoi, aramid-bridge)"),
  • Registration of the 'get_protocol' tool using server.tool(). Includes the tool name, description, input schema, and handler function.
    server.tool(
      "get_protocol",
      "Get detailed information about a specific Voi ecosystem protocol by ID",
      {
        protocolId: z
          .string()
          .describe("Protocol identifier (e.g. humble-swap, envoi, aramid-bridge)"),
      },
      async ({ protocolId }) => {
        const protocol = findProtocol(protocolId);
        if (!protocol) {
          return toolError(`Unknown protocol: ${protocolId}`);
        }
        return toolResult(protocol);
      },
    );
  • The findProtocol() helper function that searches the protocols array to find a protocol by ID. Returns the protocol object or null if not found.
    export function findProtocol(id) {
      return getProtocols().find((p) => p.id === id) || null;
    }
  • Helper functions toolResult() and toolError() used to format the tool's response output. toolResult wraps data as JSON content, toolError creates error responses.
    export function toolResult(data) {
      return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
    }
    
    export function toolError(message) {
      return {
        content: [{ type: "text", text: JSON.stringify({ error: message }) }],
        isError: true,
      };
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool retrieves information, implying it's a read-only operation, but doesn't mention any behavioral traits such as authentication requirements, rate limits, error handling, or what 'detailed information' includes. This leaves significant gaps in understanding how the tool behaves beyond its basic purpose.

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, efficient sentence that front-loads the core purpose ('Get detailed information about a specific Voi ecosystem protocol by ID'). There is no wasted wording, and every part of the sentence contributes directly to understanding the tool's function, making it highly concise and well-structured.

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?

Given the tool's simplicity (1 parameter, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose but lacks context on usage guidelines, behavioral details, and how it differs from siblings. For a read operation, this might suffice, but the absence of output information and sibling differentiation reduces completeness.

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 input schema has 100% description coverage, with the single parameter 'protocolId' documented as 'Protocol identifier (e.g. humble-swap, envoi, aramid-bridge)'. The description adds no additional meaning beyond this, as it only repeats the need for a 'protocol ID' without elaborating on format, validation, or examples. With high schema coverage, 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.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with a specific verb ('Get') and resource ('detailed information about a specific Voi ecosystem protocol by ID'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate this tool from its sibling 'get_protocol_summary' or 'get_protocols', which likely provide different levels or scopes of protocol information.

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 'get_protocol_summary' or 'get_protocols'. It mentions retrieving 'detailed information' but doesn't clarify what constitutes 'detailed' compared to other tools, leaving the agent without explicit usage context or exclusions.

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

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/MaidToShelly/UluVoiMCP'

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