Skip to main content
Glama

t2000_earnings

View yield earnings from savings positions, including total earned, daily rate, and current APY.

Instructions

View yield earnings from savings positions — total earned, daily rate, current APY. For a full account snapshot, prefer t2000_overview instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler for the 't2000_earnings' tool. It calls the agent's earnings method and returns the result as a JSON string.
    server.tool(
      't2000_earnings',
      'View yield earnings from savings positions — total earned, daily rate, current APY. For a full account snapshot, prefer t2000_overview instead.',
      {},
      async () => {
        try {
          const result = await agent.earnings();
          return { content: [{ type: 'text', text: JSON.stringify(result) }] };
        } catch (err) {
          return errorResult(err);
        }
      },
    );
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It implies a read-only operation ('View') but does not disclose behavioral traits like authentication requirements, rate limits, or error conditions. The description adds some context by specifying the data returned, but lacks details on how the tool behaves beyond its basic function.

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 highly concise and front-loaded, consisting of two sentences that efficiently convey the tool's purpose and usage guidelines without any wasted words. Every sentence adds value.

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 the tool's simplicity (0 parameters, no output schema, no annotations), the description is reasonably complete. It explains what the tool does and when to use it, but lacks details on return format or behavioral aspects, which could be improved for full completeness.

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 0 parameters with 100% schema description coverage. The description does not need to explain parameters, and it appropriately focuses on the tool's purpose and usage. A baseline of 4 is applied as it compensates adequately for the lack of parameters by providing clear context.

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 specific action ('View yield earnings') and resource ('from savings positions'), with explicit details on what data is returned ('total earned, daily rate, current APY'). It distinguishes from sibling t2000_overview by focusing narrowly on earnings rather than a full account snapshot.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly provides when to use this tool ('View yield earnings from savings positions') and when to use an alternative ('For a full account snapshot, prefer t2000_overview instead'), offering clear guidance on tool selection among siblings.

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