Skip to main content
Glama

get_protocols

List and filter Voi ecosystem protocols by type to identify services like DEX, bridges, NFT marketplaces, and naming services for blockchain exploration.

Instructions

List all known Voi ecosystem protocols with type and description

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoFilter by protocol type (dex, bridge, naming-service, nft-marketplace, etc.)

Implementation Reference

  • The handler function for the get_protocols tool. It retrieves the protocol list using getProtocols(), optionally filters by type, and returns mapped protocol data.
    async ({ type }) => {
      let list = getProtocols();
      if (type) {
        list = list.filter((p) => p.type === type);
      }
      return toolResult(
        list.map((p) => ({
          id: p.id,
          name: p.name,
          type: p.type,
          description: p.description,
          website: p.website,
          tags: p.tags,
        })),
      );
    },
  • Zod schema definition for the get_protocols tool input - defines an optional 'type' parameter for filtering protocols by type.
    type: z
      .string()
      .optional()
      .describe("Filter by protocol type (dex, bridge, naming-service, nft-marketplace, etc.)"),
  • Registration of the get_protocols tool with the MCP server. Defines the tool name, description, input schema, and handler function.
    server.tool(
      "get_protocols",
      "List all known Voi ecosystem protocols with type and description",
      {
        type: z
          .string()
          .optional()
          .describe("Filter by protocol type (dex, bridge, naming-service, nft-marketplace, etc.)"),
      },
      async ({ type }) => {
        let list = getProtocols();
        if (type) {
          list = list.filter((p) => p.type === type);
        }
        return toolResult(
          list.map((p) => ({
            id: p.id,
            name: p.name,
            type: p.type,
            description: p.description,
            website: p.website,
            tags: p.tags,
          })),
        );
      },
    );
  • Helper function that loads and returns the protocols data from protocols.json file. Uses lazy loading with caching.
    export function getProtocols() {
      if (!protocols) protocols = loadJSON("protocols.json");
      return protocols;
    }
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 list operation, implying it's read-only and non-destructive, but doesn't address potential limitations like pagination, rate limits, or authentication requirements. The description adds minimal behavioral context beyond the basic action.

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 without unnecessary words. It directly communicates what the tool does, making it easy to parse and understand quickly.

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 low complexity (one optional parameter, no output schema, no annotations), the description is adequate but minimal. It covers the basic purpose but lacks context on usage guidelines, behavioral traits, or output details, leaving gaps for an agent to infer correct invocation.

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 single parameter 'type' documented as a filter for protocol types. The description adds no additional parameter semantics beyond what the schema provides, such as examples or usage nuances. 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 action ('List all known') and resource ('Voi ecosystem protocols') with specific attributes ('with type and description'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like get_protocol or get_protocol_summary, which likely provide more detailed or filtered 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 such as get_protocol or get_protocol_summary. It mentions filtering by type in the parameter description, but this is part of the input schema, not explicit usage instructions for tool selection.

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