Skip to main content
Glama

DeFAI Intent Solver, Yield Optimizer & Kelly Execution Router MCP

DeFAI Intent Solver: Kelly Sizing, Top Yield Vault & 0.25% Non-Custodial Execution

solve_defai_yield_and_execution_intent
Read-onlyIdempotent

Resolves autonomous DeFAI agent intents ('maximize_stable_yield', 'fund_prediction_arb', 'delta_neutral_carry') into Half-Kelly position sizing, live >$5M TVL vault selection, and ready-to-sign 0.25% non-custodial swap or cross-chain USDC execution routes.

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

Input Schema

NameRequiredDescriptionDefault
amountNoInput asset amount (default 0.5)
senderNoOptional 0x wallet address
chainIdNoSource EVM chain ID ('8453' Base, '42161' Arbitrum, '137' Polygon, '10' Optimism, '1' Ethereum)
srcTokenNoInput asset symbol such as 'ETH' or 'USDC' (default 'ETH')
intentTypeNo'maximize_stable_yield', 'fund_prediction_arb', or 'delta_neutral_carry'
marketYesPriceNoOptional current market YES share price (0.01-0.99)
estimatedWinProbPctNoOptional agent true probability % (1-99) for Half-Kelly prediction sizing

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world, and non-destructive, so the bar is lower; the description still adds real behavior — a 0.25% fee, a >$5M TVL vault filter, Half-Kelly sizing, and non-custodial 'ready-to-sign' output (i.e. it builds routes rather than executing them). It stops short of saying whether anything is submitted on-chain or how the response is shaped.

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?

One dense but front-loaded sentence that leads with the verb and the intent vocabulary before the output list. Jargon-heavy, but no sentence is wasted and nothing is buried.

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 seven-parameter, all-optional tool with no output schema, the definition explains what the solver produces but not which parameters matter for which intent — notably that marketYesPrice and estimatedWinProbPct only drive the prediction-arb path. An agent can call it, but it may omit the inputs that make a given intent meaningful.

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 coverage is 100%, so the schema already documents all seven parameters and their allowed values. The description only loosely maps fields to behavior (Kelly sizing implies the probability params, vault selection implies chain/token/amount) without adding format or dependency details, so the baseline 3 applies.

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?

States a specific verb ('Resolves') and resource ('DeFAI agent intents'), enumerates the three accepted intent strings, and names the three outputs (Half-Kelly sizing, vault selection, execution routes). It is clearly distinct from single-purpose siblings like quote_low_fee_dex_swap or get_institutional_stable_yields, though it never names an alternative explicitly.

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 enumerated intent types imply the triggering context (an agent that already holds a named intent), but there is no explicit when-to-use vs. when-not, and no routing guidance against the many single-purpose siblings that overlap on vaults, quoting, and swap calldata.

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.