Skip to main content
Glama

MCP Apps Interactive DeFi, Polymarket & RWA Checkout Terminal UI

DeFAI Intent Solver: Kelly Sizing, Top Yield Vault & 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 non-custodial execution routes. Includes interactive MCP App UI.

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 declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safety profile is covered; the description adds genuinely new behavior: output is 'ready-to-sign' and 'non-custodial', meaning nothing is broadcast, and vault selection is filtered to live >$5M TVL. That reconciles the read-only annotation with the execution language, which an agent could otherwise misread as a write operation.

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 dense sentence that front-loads the verb, the intent domain, and the three outputs, followed by a short note about the interactive UI. No filler, though the packing of three outputs plus a UI note into one sentence makes it slightly harder to scan.

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 7-parameter, zero-required-parameter tool with no output schema, the description should sketch what comes back (sizing numbers, chosen vault, route calldata); it names the outputs but gives no shape or units. The absent required parameters also go unexplained, leaving an agent unsure whether a bare call is valid.

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 every parameter is already documented, including chain IDs, token symbols, and the 1-99 probability range. The description adds only indirect meaning by tying 'Half-Kelly' to estimatedWinProbPct and marketYesPrice; it does not explain parameter interactions or defaults beyond what the schema states.

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 gives a specific verb ('Resolves') plus the resource ('autonomous DeFAI agent intents') and enumerates the three intent types it handles, along with the three concrete outputs (Half-Kelly sizing, vault selection, execution routes). It is clear what the tool does, though it never contrasts itself with siblings like get_institutional_stable_yields or quote_low_fee_dex_swap, which overlap in the yield/swap space.

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 through the enumerated intent strings ('maximize_stable_yield', 'fund_prediction_arb', 'delta_neutral_carry'), which signal the situations the tool is built for. There is no explicit when-to-use vs. when-not guidance and no named alternative for an agent that just wants a raw quote or a plain swap.

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.