Skip to main content
Glama

Liquidity reward eligibility

pm_reward_eligibility
Read-only

Whether a resting order qualifies for a market's daily liquidity rewards (minimum size, maximum distance to midpoint), exactly what is missing if it does not, and an estimate of the daily payout.

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": {
      "shares": "<shares>",
      "spread_cents": "<spread_cents>",
      "rewards_min_size": "<rewards_min_size>",
      "rewards_max_spread": "<rewards_max_spread>"
    },
    "name": "pm_reward_eligibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
sharesYes
daily_potNo
spread_centsYes
competing_sharesNo
rewards_min_sizeYes
rewards_max_spreadYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description's real contribution is disclosing the shape of the result — a pass/fail verdict, a diagnosis of exactly what is missing when it fails, and a daily payout estimate — which matters because no output schema exists. It stops short of saying whether the payout figure is an estimate under stated assumptions, what happens with zero competing_shares, or whether rewards rules are per-market configuration.

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?

A single front-loaded sentence that leads with the verdict and then enumerates the secondary outputs. No filler or restatement of the title. It is dense to the point of being a run-on, which slightly hurts scanability but wastes no words.

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

Completeness3/5

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

The description compensates well for the missing output schema by describing the three return components. However, for a six-parameter tool with zero schema documentation and no enums, the input side is under-specified: an agent cannot know what shares or competing_shares represent or how spread_cents is measured, which risks incorrect invocation.

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 0% across six parameters, so the description carries the burden. It partially maps three inputs — minimum size (rewards_min_size), maximum distance to midpoint (rewards_max_spread), and payout estimation (daily_pot) — but leaves shares, spread_cents, and competing_shares completely unexplained, including units and sign conventions for spread. Significant meaning is still missing despite the useful partial hints.

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 a specific evaluation ('whether a resting order qualifies for a market's daily liquidity rewards') plus the qualifying criteria and the two outputs it produces. An agent can immediately tell this is a read-only eligibility check rather than an order or fee operation. It does not explicitly contrast with the siblings (pm_market_brief, pm_order_book_fill, pm_platform_fee), but those are functionally distinct enough that confusion is unlikely.

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?

Usage is only implied: the description makes clear you call it when you have a resting order whose reward eligibility you want evaluated. There is no explicit when-not guidance, no note about preconditions (e.g., that the market must actually run a rewards program), and no pointer to an alternative tool for the payout side versus eligibility side.

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