Skip to main content
Glama
Sign In
Bit2Me MCP Server

Bit2Me MCP Server

by bit2me-devs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

earn_get_position_rewards_config

Read-onlyIdempotent

Retrieve reward calculation rules, APY details, and staking parameters for a specific Earn position using its position ID to clarify expected returns.

Instructions

Get rewards configuration for a specific Earn position. Returns reward calculation rules, APY details, and position-specific staking parameters. Use earn_get_positions first to get the position ID. [PRIVATE]

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "position_id": "<position_id>"
    },
    "name": "earn_get_position_rewards_config"
  }
}

Input Schema

NameRequiredDescriptionDefault
jwtNoOptional session token for authentication. API keys are recommended for most use cases.
position_idYesEarn position UUID from earn_get_positions

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.1.4

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds return-content context but does not explain the [PRIVATE] marker, auth requirements, rate limits, or error 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 three short sentences with zero filler: core action, return contents, prerequisite. It is front-loaded with the main purpose and keeps supporting details compact.

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 read-only two-parameter tool with rich annotations, the description provides the prerequisite and high-level return contents. Without an output schema, a bit more detail about the response shape would help, but the gaps are minor.

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?

The schema already documents both parameters fully at 100% coverage, including position_id's UUID format and jwt's optional session-token purpose. The description only reinforces that position_id comes from earn_get_positions, adding little beyond the schema.

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 states a specific verb and resource: 'Get rewards configuration for a specific Earn position.' It also lists what is returned (reward calculation rules, APY details, position-specific staking parameters), and the word 'specific' plus 'position-specific' helps distinguish it from the sibling earn_get_rewards_config.

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?

The description gives an explicit prerequisite: 'Use earn_get_positions first to get the position ID.' It does not explicitly name alternatives like earn_get_position_rewards_summary or say when not to use them, but the usage context is clear.

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