Skip to main content
Glama

exergynet_verify_program

Verify if program LNES-01 is live on Mainnet by providing an RPC URL.

Instructions

Check if LNES-01 is live on Mainnet.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rpcUrlNo

Implementation Reference

  • src/index.ts:20-20 (registration)
    Registration of the 'exergynet_verify_program' tool in the ListToolsRequestSchema handler, defining its name, description, and input schema (optional rpcUrl string).
    { name: "exergynet_verify_program", description: "Check if LNES-01 is live on Mainnet.", inputSchema: { type: "object", properties: { rpcUrl: { type: "string" } }, additionalProperties: false } },
  • Input schema for exergynet_verify_program: accepts an optional 'rpcUrl' string property. No additional properties allowed.
    { name: "exergynet_verify_program", description: "Check if LNES-01 is live on Mainnet.", inputSchema: { type: "object", properties: { rpcUrl: { type: "string" } }, additionalProperties: false } },
  • Handler implementation: takes an optional rpcUrl (defaults to Solana mainnet), creates a Solana connection, fetches the account info for the ExergyNet program ID (Fe8KhdiFWhKcPWH2N2Svqc3VSpK9EzN8nMh9pQ3cPCeD), and returns JSON with 'exists' (boolean) and 'executable' (nullable boolean).
    case "exergynet_verify_program": {
      const rpcUrl = (args.rpcUrl as string) || DEFAULT_RPC;
      const connection = new Connection(rpcUrl, "confirmed");
      const info = await connection.getAccountInfo(new PublicKey(EXERGYNET_PROGRAM_ID));
      return { content:[{ type: "text", text: JSON.stringify({ exists: info !== null, executable: info?.executable }) }] };
    }
Behavior1/5

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

No annotations are provided, and the description fails to disclose behavioral traits such as whether the tool queries a blockchain, if it is read-only, or any side effects. The term 'check' is vague.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is a single sentence, which is concise, but lacks structured information. It is too brief to be fully effective.

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

Completeness1/5

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

The tool has no output schema and the description does not explain the return value, what 'live' means, or how to interpret results. The description is inadequate for an agent to use the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description mentions 'Mainnet' but does not explain the purpose of the 'rpcUrl' parameter. With 0% schema description coverage, the description should compensate but fails to provide meaningful parameter guidance.

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 (check) and the specific resource (LNES-01 on Mainnet), distinguishing it from sibling tools which have different purposes (estimate_gate, get_program_id, get_proof_transaction).

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 on when to use this tool versus alternatives, or any context about prerequisites or limitations. The description only states what it does without usage context.

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/ezumba/exergynet-mcp-server'

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