Skip to main content
Glama
Sign In

SimianX AI

by io.github.SimianX-AI
OverviewDiscussionsAdmin

Claim the daily reward

claim_daily_reward

Claim the user's free daily reward when they ask for it ("try my luck"): today's, else an extra claim. No purchase or money involved. Tell them what they got (prize.name, benefits) and their streak.

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

Input Schema

NameRequiredDescriptionDefault
request_idNoOptional: a retry with the same one the same day returns the same reward; a second claim the same day (an extra draw) needs a new one
idempotency_keyNoOptional: any unique string for this action; send the same one when retrying the same call and the first result comes back instead of the action running twice

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the annotations (mutation, non-idempotent, free-form/open-world), the description discloses that there is no purchase or money involved, that a claim may resolve to today's reward or an extra draw, and that the agent should surface prize.name, benefits, and the streak. With no output schema, that response-shaping detail is genuinely additive. It does not cover error cases such as what happens if today's reward is already claimed.

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?

Three short sentences, front-loaded with the action and its trigger, with no wasted framing. The phrase 'today's, else an extra claim' is slightly elliptical but readable in context.

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?

For a parameterless-required mutation with no output schema, the description supplies what the agent needs: when to call, that no money is involved, and which result fields to report back. Only failure/duplicate-claim handling is left implicit.

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 both request_id and idempotency_key are documented in the schema, including the retry vs. extra-draw distinction. The description adds nothing about either parameter, so the baseline 3 applies.

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 names a specific verb and resource ('Claim the user's free daily reward') and adds the trigger phrase users actually say ('try my luck'), which separates it cleanly from the read-only sibling get_daily_reward.

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 clearly states the condition for calling it ('when they ask for it') and explains the fallback behavior ('today's, else an extra claim'). It does not name get_daily_reward as the alternative for checking status instead of claiming, so guidance is strong but not exhaustive.

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

All SimianX AI toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources