Skip to main content
Glama
Sign In
Toleno Network MCP Server

Toleno Network MCP Server

Official
by tolenonetwork
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

claim_mining

Claim mining rewards after a completed 24-hour session. Collects tokens and updates your balance.

Instructions

Claim mining rewards after a completed 24-hour session. Can only be called when a session has ended and rewards are ready to collect. Returns the amount of tokens claimed and the new balance.

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": "claim_mining"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses the return values but omits behavioral traits like whether the action is irreversible, if special permissions are needed, or rate limits. More detail would improve transparency.

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?

Three concise sentences, each carrying essential information: action, condition, and return value. No fluff or redundancy.

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 no input schema complexity and no output schema, the description provides sufficient context: what it does, when to call, and what it returns. It could mention user authentication, but it's adequate for an agent.

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?

The tool has zero parameters, and schema coverage is 100%. The description adds no parameter info because none is needed. Baseline for 0 parameters is 4, which is appropriate.

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 the tool's action ('Claim mining rewards'), the condition ('after a completed 24-hour session'), and what it returns ('amount of tokens claimed and the new balance'). It effectively distinguishes from siblings like start_mining and get_mining_status.

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?

It explicitly states the prerequisite ('Can only be called when a session has ended and rewards are ready to collect'), providing clear usage context. While it doesn't name specific alternative tools, the condition is sufficient for an agent to determine when to invoke.

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