Skip to main content
Glama

identify_application

Identify Voi blockchain applications by ID to retrieve protocol details, role, type, and description information for ecosystem analysis.

Instructions

Identify a Voi application by ID — returns protocol, role, type, and description if known

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appIdYesApplication ID on Voi

Implementation Reference

  • The async handler function that executes the identify_application tool logic. It takes an appId parameter, looks up the application in the registry using findApplication(), retrieves protocol information if available, and returns structured results with application details or a 'not found' message.
    async ({ appId }) => {
      const app = findApplication(appId);
      if (!app) {
        return toolResult({
          appId,
          known: false,
          message: `Application ${appId} is not in the Voi ecosystem registry`,
        });
      }
      const protocol = app.protocol ? findProtocol(app.protocol) : null;
      return toolResult({
        appId,
        known: true,
        name: app.name,
        protocol: app.protocol,
        protocolName: protocol?.name || null,
        type: app.type,
        role: app.role,
        description: app.description,
        tokens: app.tokens || null,
      });
    },
  • Zod schema definition for the identify_application tool input. Validates that appId is an integer number and provides a description for the parameter.
      appId: z
        .number()
        .int()
        .describe("Application ID on Voi"),
    },
  • tools/identify.js:6-37 (registration)
    Complete tool registration using server.tool() method. Registers the 'identify_application' tool with its description, input schema, and handler function.
    server.tool(
      "identify_application",
      "Identify a Voi application by ID — returns protocol, role, type, and description if known",
      {
        appId: z
          .number()
          .int()
          .describe("Application ID on Voi"),
      },
      async ({ appId }) => {
        const app = findApplication(appId);
        if (!app) {
          return toolResult({
            appId,
            known: false,
            message: `Application ${appId} is not in the Voi ecosystem registry`,
          });
        }
        const protocol = app.protocol ? findProtocol(app.protocol) : null;
        return toolResult({
          appId,
          known: true,
          name: app.name,
          protocol: app.protocol,
          protocolName: protocol?.name || null,
          type: app.type,
          role: app.role,
          description: app.description,
          tokens: app.tokens || null,
        });
      },
    );
  • index.js:13-13 (registration)
    Invokes registerIdentifyTools(server) to register all identify tools including identify_application with the MCP server instance.
    registerIdentifyTools(server);
  • Helper function findApplication() used by the handler to look up application data by ID from the loaded applications registry JSON.
    export function findApplication(appId) {
      const apps = getApplications();
      return apps[String(appId)] || null;
    }
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 return fields but doesn't cover important aspects like error handling, authentication needs, rate limits, or whether this is a read-only operation. The description is too minimal for a tool with no annotation support.

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 extremely concise and front-loaded with essential information in a single sentence. Every word serves a purpose with no wasted text, making it easy for an agent to parse quickly.

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 no annotations and no output schema, the description is incomplete. It mentions return fields but doesn't explain their format, potential null values, or error conditions. For a tool that presumably queries an external system, more behavioral context is needed.

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%, so the schema already documents the single 'appId' parameter. The description doesn't add any meaningful parameter semantics beyond what the schema provides, such as format examples or constraints. 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 action ('identify') and resource ('Voi application by ID'), specifying what information is returned (protocol, role, type, description). However, it doesn't explicitly differentiate this tool from its siblings like 'identify_asset' or 'resolve_name', which prevents 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. It doesn't mention prerequisites, context, or exclusions, leaving the agent with no usage direction beyond the basic purpose.

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