Skip to main content
Glama

risk_adjusted

πŸ”’ PREMIUM (not available anonymously on this endpoint): APY adjusted for risk β€” pools ranked by real expected return after factoring liquidity, volatility, IL, and sustainability. The smart way to compare yields.

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": "risk_adjusted"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoResults (default: 15)
queryNoFilter by token/protocol (optional)
min_tvlNoMin TVL (default: 100000)
pool_idNoSpecific pool ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses premium/non-anonymous access and the ranking factors, but does not describe return shape, pagination, rate limits, or other operational behavior.

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?

The description is short and front-loads the premium access restriction and core purpose. The phrase 'The smart way to compare yields' is slight marketing filler but does not seriously detract from clarity.

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?

For a complex ranking tool with no annotations and no output schema, the description explains methodology and auth requirements but omits return fields and operational details. Input parameters are fully covered by the schema, but the absence of output schema means return expectations are not fully addressed.

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 100%, so the schema already documents limit, query, min_tvl, and pool_id. The description adds no additional parameter-specific meaning beyond what the schema provides, making the baseline score appropriate.

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 states a specific operation: APY adjusted for risk, with pools ranked by real expected return after liquidity, volatility, IL, and sustainability. It distinguishes itself from generic yield tools by the risk-adjustment concept, though it does not explicitly name or compare against siblings like yield_compare or top_yields.

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?

The premium access note gives important usage context, and 'The smart way to compare yields' implies this is for yield comparison. However, there is no explicit guidance on when to choose this over the many sibling yield tools or when not to use it.

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.