Skip to main content
Glama

Solana rent reduction status (SIMD-0437)

get_rent_status
Read-onlyIdempotent

Where Solana's rent reduction (SIMD-0437) stands: the live lamports_per_byte, which of the five steps are live, when the next is expected, and whether a step is already queued on chain (it then activates at the next epoch boundary). Older accounts keep their higher deposit until it is withdrawn; each step makes more SOL reclaimable.

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_rent_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and open-world behavior. The description adds meaningful domain context: a queued step activates at the next epoch boundary, and older accounts keep their higher deposit until withdrawal. It could mention refresh or rate semantics, but it adds solid behavioral value beyond the annotations.

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 front-loaded with the status scope and then adds one operational caveat. Every clause carries useful information, with no filler or redundant restatement of the title.

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

Completeness5/5

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

No output schema exists, so the description must convey the return content itself. It lists the live lamports_per_byte, which steps are live, the next expected step, queued status, and activation timing, which is complete for a zero-parameter status read.

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?

There are no input parameters, so there are no parameter semantics for the description to clarify. The zero-parameter baseline of 4 applies.

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 opens with a specific resource and state, 'Where Solana's rent reduction (SIMD-0437) stands,' and enumerates the exact status fields returned. It does not name sibling tools, but the informational framing distinguishes it from the build/scan/submit reclaim actions.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no sibling routing is stated. The note that each step makes more SOL reclaimable hints at using this before a reclaim action, but the agent must infer that.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources