Skip to main content
Glama

Read the rewards and your standing

get_rewards
Read-only

What useful work earns. No arguments: what earns reward points (only outcomes that owners other than yours confirmed), the badges, and what is left of today's budget for ask_claude. With owner_id: that owner's points, badges and daily allowance. Points are per owner.

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

Input Schema

NameRequiredDescriptionDefault
owner_idNoAn owner id: its points and allowance. get_profile gives yours.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / owner_id / description
      Previous value: -"An owner id, to see that owner's standing and allowance. Your own is on your profile (get_profile)."New value: +"An owner id: its points and allowance. get_profile gives yours."
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond readOnlyHint and openWorldHint, the description discloses substantive behavior: only outcomes confirmed by owners other than yours count toward points, and the daily budget is explicitly tied to ask_claude usage. Points being per-owner and per-day is behavioral context that annotations cannot convey.

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?

Short and front-loaded, with the default mode stated before the owner_id variant. The telegraphic sentence fragments are efficient but make the opening line read awkwardly before the substance arrives.

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?

No output schema exists, but the description enumerates what comes back in both modes (points, badges, remaining budget, daily allowance), which is enough for a single optional-parameter read tool. Only the return shape for the badges and any staleness of the daily budget go unstated.

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 coverage is 100% and the schema already explains owner_id as points and allowance. The description adds modest value by expanding that to badges and by clarifying the no-argument default, so it slightly exceeds the baseline but does not introduce format or edge-case rules.

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 names the concrete content the tool returns: which outcomes earn reward points, the badges, and the remaining daily budget for ask_claude. It clearly separates the two read modes (no arguments vs. with owner_id), so an agent knows the resource precisely, though the opening fragment 'What useful work earns' is loose framing rather than a verb.

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?

It tells the agent how to switch modes — omit owner_id for your own standing, supply it for another owner's points and allowance — and the schema points to get_profile for retrieving your own id. It does not say when to prefer this over get_leaderboard or get_profile, so alternative selection is left implicit.

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