Skip to main content
Glama

get_protocol_summary

Generate human-readable summaries of Voi protocols including purpose, contracts, and assets to understand blockchain ecosystem services.

Instructions

Get a human-readable summary of a Voi protocol including its purpose, contracts, and assets

Input Schema

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

Implementation Reference

  • The handler function for get_protocol_summary tool. It retrieves protocol details, contracts, and assets, then formats them into a human-readable markdown summary with sections for type, website, description, contracts (grouped by type), assets, and tags.
      async ({ protocolId }) => {
        const protocol = findProtocol(protocolId);
        if (!protocol) {
          return toolError(`Unknown protocol: ${protocolId}`);
        }
        const contracts = protocolContracts(protocolId);
        const assets = protocolAssets(protocolId);
    
        const lines = [
          `# ${protocol.name}`,
          ``,
          `**Type:** ${protocol.type}`,
          `**Website:** ${protocol.website || "N/A"}`,
          ``,
          protocol.description,
          ``,
          `## Contracts (${contracts.length})`,
        ];
    
        const byType = {};
        for (const c of contracts) {
          const t = c.type || "other";
          if (!byType[t]) byType[t] = [];
          byType[t].push(c);
        }
        for (const [type, items] of Object.entries(byType)) {
          lines.push(`- **${type}**: ${items.length} contract(s)`);
          for (const item of items.slice(0, 5)) {
            lines.push(`  - ${item.appId}: ${item.name}`);
          }
          if (items.length > 5) {
            lines.push(`  - ... and ${items.length - 5} more`);
          }
        }
    
        if (assets.length > 0) {
          lines.push(``, `## Assets (${assets.length})`);
          for (const a of assets) {
            lines.push(`- ${a.symbol} (${a.assetId}): ${a.name} — ${a.category}`);
          }
        }
    
        lines.push(``, `**Tags:** ${(protocol.tags || []).join(", ")}`);
    
        return { content: [{ type: "text", text: lines.join("\n") }] };
      },
    );
  • Zod schema definition for the protocolId input parameter, requiring a string that describes the protocol identifier (e.g. humble-swap, envoi, aramid-bridge).
    {
      protocolId: z
        .string()
        .describe("Protocol identifier (e.g. humble-swap, envoi, aramid-bridge)"),
    },
  • Registration of the get_protocol_summary tool with the MCP server using server.tool(), including the tool name, description, input schema, and handler function.
    server.tool(
      "get_protocol_summary",
      "Get a human-readable summary of a Voi protocol including its purpose, contracts, and assets",
      {
        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}`);
        }
        const contracts = protocolContracts(protocolId);
        const assets = protocolAssets(protocolId);
    
        const lines = [
          `# ${protocol.name}`,
          ``,
          `**Type:** ${protocol.type}`,
          `**Website:** ${protocol.website || "N/A"}`,
          ``,
          protocol.description,
          ``,
          `## Contracts (${contracts.length})`,
        ];
    
        const byType = {};
        for (const c of contracts) {
          const t = c.type || "other";
          if (!byType[t]) byType[t] = [];
          byType[t].push(c);
        }
        for (const [type, items] of Object.entries(byType)) {
          lines.push(`- **${type}**: ${items.length} contract(s)`);
          for (const item of items.slice(0, 5)) {
            lines.push(`  - ${item.appId}: ${item.name}`);
          }
          if (items.length > 5) {
            lines.push(`  - ... and ${items.length - 5} more`);
          }
        }
    
        if (assets.length > 0) {
          lines.push(``, `## Assets (${assets.length})`);
          for (const a of assets) {
            lines.push(`- ${a.symbol} (${a.assetId}): ${a.name} — ${a.category}`);
          }
        }
    
        lines.push(``, `**Tags:** ${(protocol.tags || []).join(", ")}`);
    
        return { content: [{ type: "text", text: lines.join("\n") }] };
      },
    );
  • findProtocol helper function that searches the protocols list to find a protocol by its ID, returning null if not found.
    export function findProtocol(id) {
      return getProtocols().find((p) => p.id === id) || null;
    }
  • protocolContracts and protocolAssets helper functions that filter applications and assets by protocol ID, returning arrays with appId/assetId and their associated info.
    export function protocolContracts(protocolId) {
      const apps = getApplications();
      const results = [];
      for (const [appId, info] of Object.entries(apps)) {
        if (info.protocol === protocolId) {
          results.push({ appId: Number(appId), ...info });
        }
      }
      return results;
    }
    
    export function protocolAssets(protocolId) {
      const a = getAssets();
      const results = [];
      for (const [assetId, info] of Object.entries(a)) {
        if (info.protocol === protocolId) {
          results.push({ assetId: Number(assetId), ...info });
        }
      }
      return results;
    }
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 a summary but doesn't cover aspects like whether it's a read-only operation, potential rate limits, authentication needs, or error handling. This is a significant gap 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads the key action and resource. It avoids unnecessary words, though it could be slightly more structured by explicitly listing the tool's output format or limitations.

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 adequate but incomplete. It covers the purpose but lacks behavioral context and usage guidelines, which are needed for a tool with no annotations to be fully helpful.

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 'protocolId' fully documented in the schema. The description doesn't add any parameter-specific details beyond what the schema provides, such as examples or constraints, so it 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 action ('Get a human-readable summary') and resource ('a Voi protocol'), specifying what information is included ('purpose, contracts, and assets'). However, it doesn't explicitly differentiate from sibling tools like 'get_protocol' or 'get_protocol_contracts', which likely provide more technical or detailed data.

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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention sibling tools or contexts where a human-readable summary is preferred over other protocol-related tools, leaving usage decisions unclear.

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