Skip to main content
Glama

get_next_maintenance_time

Read-only

Retrieves the timestamp of the next TRON network maintenance window, optionally for a specified network, so you can plan around scheduled downtime.

Instructions

Get the timestamp of the next network maintenance window.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_next_maintenance_time"
  }
}

Input Schema

NameRequiredDescriptionDefault
networkNoNetwork name. Defaults to mainnet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.9
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.1.7

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false and idempotentHint=false, so the safety and volatility profile is covered. Beyond that the description only adds that a timestamp is returned; it says nothing about format, timezone, or what happens when no maintenance is scheduled.

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?

One sentence, front-loaded with the verb and the returned value, and no redundant restatement of the title or annotations. Nothing in it is wasted.

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?

For a simple one-optional-parameter read with no output schema, the core is present: it says the return is a timestamp for the next maintenance window. It is still thin on return details (format/timezone) and on the no-maintenance-scheduled case, which an agent would need for the openWorldHint network call.

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?

Schema description coverage is 100% and the single 'network' parameter is documented in-schema with its mainnet default, so the schema carries the burden. The description adds no meaning about the parameter or the effect of choosing a different network.

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?

States a specific verb and resource ('Get the timestamp of the next network maintenance window'), making the returned value explicit rather than restating the name. It does not differentiate from any sibling, but the sibling list contains no obviously overlapping maintenance/time tool, so ambiguity is low.

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?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. The intent (checking upcoming maintenance before scheduling work) is only implied by the phrase 'next network maintenance window'.

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