Skip to main content
Glama

t2000_claim_rewards

Claim pending protocol rewards from lending positions and automatically convert them to USDC.

Instructions

Claim pending protocol rewards from lending positions and auto-convert to USDC.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler implementation for the tool 't2000_claim_rewards'. It invokes 'agent.claimRewards()' within a mutex lock to safely claim and convert protocol rewards.
    server.tool(
      't2000_claim_rewards',
      'Claim pending protocol rewards from lending positions and auto-convert to USDC.',
      {},
      async () => {
        try {
          const result = await mutex.run(() => agent.claimRewards());
          return { content: [{ type: 'text', text: JSON.stringify(result) }] };
        } catch (err) {
          return errorResult(err);
        }
      },
    );
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'claim' and 'auto-convert to USDC', implying a write operation with conversion, but fails to detail critical aspects like required permissions, transaction costs, rate limits, or whether the action is irreversible. This leaves significant gaps in understanding the tool's behavior.

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 a single, efficient sentence that directly states the tool's function without any redundant or verbose language. It is front-loaded with the core action and outcome, making it easy to parse and understand quickly.

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

Completeness2/5

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

Given the complexity of a financial transaction tool with no annotations and no output schema, the description is insufficient. It omits details on return values, error conditions, side effects (e.g., impact on balances), and integration with sibling tools. For a tool that likely involves blockchain interactions, more context is needed for safe and effective use.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately adds no parameter details, focusing on the tool's action and outcome. A baseline of 4 is applied since the schema fully covers the lack of parameters, and the description doesn't attempt to compensate unnecessarily.

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 clearly states the action ('claim') and target ('pending protocol rewards from lending positions') with the additional outcome ('auto-convert to USDC'), making the purpose specific. However, it doesn't explicitly differentiate from sibling tools like 't2000_pending_rewards' (which might list rather than claim rewards), leaving room for improvement.

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?

The description provides no guidance on when to use this tool versus alternatives, such as whether it should be triggered after checking 't2000_pending_rewards' or in response to specific conditions. It lacks any mention of prerequisites, exclusions, or recommended contexts, offering minimal usage direction.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mission69b/t2000'

If you have feedback or need assistance with the MCP directory API, please join our Discord server