Skip to main content
Glama
Sign In
mcp-server-justlend

mcp-server-justlend

Official
by justlend
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

calculate_energy_rental_price

Read-only

Calculate energy rental cost on TRON for new or renewal orders. Returns TRX amount, fees, security deposit, and daily cost, with auto-detection of existing rentals.

Instructions

Calculate the cost to rent a specific amount of energy for a given duration. Returns TRX amount needed, rental rate, fee, total prepayment, security deposit, and daily cost. For NEW rentals: provide energyAmount and durationHours. For RENEWALS: provide energyAmount and receiverAddress. The tool auto-detects existing rentals and calculates the incremental cost (subtracting existing security deposit). durationHours is optional for renewals (defaults to 0 = no additional time).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "energyAmount": "<energyAmount>"
    },
    "name": "calculate_energy_rental_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
networkNoNetwork. Default: mainnet
energyAmountYesAmount of energy to rent (minimum 300,000 for new rental, minimum 50,000 for renewal)
durationHoursNoRental duration in hours. Required for new rentals (minimum 1). Optional for renewals (default 0 = no additional time).
receiverAddressNoReceiver address. If provided, checks for existing rental to calculate renewal cost.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already show readOnlyHint=true, so the description's behavioral context about auto-detection and incremental cost calculation adds value beyond annotations. It discloses that for renewals it subtracts existing security deposit, which is a key behavioral detail.

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 about 100 words, front-loaded with the core purpose, and well-structured with separate sections for new and renewals. It could be slightly more concise but no unnecessary information.

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?

The description lists return values (important since there's no output schema), explains auto-detection for renewals, and gives parameter context. It could specify units or output format, but overall it's sufficient for an agent to use correctly.

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?

Schema coverage is 100% but the description adds meaning by clarifying the different minimums for new (300,000) vs renewal (50,000) and the conditional requirement of durationHours. This goes beyond the schema's generic 'minimum 50,000' and 'required for new' context.

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?

The description clearly states it calculates the cost to rent energy for a given duration, and distinguishes between new rentals and renewals. It lists the specific return values, and the contrast with siblings like 'get_energy_rental_rate' (rate only) and 'rent_energy' (executes) is implicit.

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

Usage Guidelines4/5

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

The description explicitly tells when to use each parameter combination (new vs renewal) and mentions auto-detection of existing rentals. It does not explicitly list when not to use this tool, but the context of siblings and the detailed parameter guidance make it clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools