Skip to main content
Glama

exergynet_get_program_id

Retrieves the Mainnet LNES-01 program ID for thermodynamic compute settlement on ExergyNet.

Instructions

Return the Mainnet LNES-01 program ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:19-19 (registration)
    Tool registration in the ListToolsRequestSchema handler. Defines the tool name, description, and empty inputSchema.
    { name: "exergynet_get_program_id", description: "Return the Mainnet LNES-01 program ID.", inputSchema: { type: "object", properties: {} } },
  • Handler logic for the 'exergynet_get_program_id' tool. Returns the constant EXERGYNET_PROGRAM_ID as text content.
    case "exergynet_get_program_id": return { content:[{ type: "text", text: EXERGYNET_PROGRAM_ID }] };
  • Constant definition for EXERGYNET_PROGRAM_ID = 'Fe8KhdiFWhKcPWH2N2Svqc3VSpK9EzN8nMh9pQ3cPCeD'
    const EXERGYNET_PROGRAM_ID = "Fe8KhdiFWhKcPWH2N2Svqc3VSpK9EzN8nMh9pQ3cPCeD";
  • dist/index.js:15-15 (registration)
    Compiled registration in dist/index.js
    { name: "exergynet_get_program_id", description: "Return the Mainnet LNES-01 program ID.", inputSchema: { type: "object", properties: {} } },
  • Compiled handler in dist/index.js returning EXERGYNET_PROGRAM_ID
    case "exergynet_get_program_id": return { content: [{ type: "text", text: EXERGYNET_PROGRAM_ID }] };
Behavior2/5

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

No annotations are provided, and the description only says 'Return the Mainnet LNES-01 program ID'. It does not disclose behavioral traits such as whether it requires authentication, has side effects, or returns format specifics. For a read operation, more transparency would be beneficial.

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?

Description is a single, front-loaded sentence. It is concise, though it could further clarify that no inputs are required.

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

Completeness4/5

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

Given zero parameters, no output schema, and a simple purpose, the description is mostly complete. It clearly states what is returned. However, it does not specify the data type of the program ID (e.g., string, number).

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

Parameters4/5

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

Input schema has zero parameters with 100% coverage. Description adds nothing about parameters because none exist. Baseline of 4 is appropriate as it correctly indicates no arguments needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

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

Description clearly states 'Return the Mainnet LNES-01 program ID', using a specific verb and resource. It distinguishes from siblings like exergynet_estimate_gate, exergynet_get_proof_transaction, and exergynet_verify_program, which handle different operations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Description does not explicitly state when or when not to use this tool. It implies usage when the program ID is needed, but lacks explicit context or alternative guidance.

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