Skip to main content
Glama
Sign In
DeFi Quant Multi-Protocol Yield & Risk API

DeFi Quant Multi-Protocol Yield & Risk API

by Pyrochem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Fluid LiquidityLayer Bit-Unpacker & Simulator

unpack_fluid_liquidity_layer_state
Read-onlyIdempotent

Decodes Fluid LiquidityLayer BigMath storage slots and simulates post-trade utilization to report USDC borrow and supply rates.

Instructions

Use this tool when a user asks about Fluid Protocol USDC borrow/supply rates, needs to decode Fluid's 256-bit BigMath storage slots (exchangePricesAndConfig), or wants to simulate post-trade utilization on Fluid.

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

Input Schema

NameRequiredDescriptionDefault
tokenAddressNoERC-20 token address on Fluid LiquidityLayer (defaults to Mainnet USDC)
simBorrowDeltaNoSimulated additional borrow amount in token units (default: 2000000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.7

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare this read-only, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds the useful nuance that it performs hypothetical simulation via simBorrowDelta on live on-chain state, which is not obvious for a 'readOnly' tool. However it says nothing about what the unpack returns (field layout of the 256-bit slot, rate outputs) or whether RPC access/latency applies.

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 sentence, front-loaded with the trigger clause and zero filler. It is jargon-dense ('BigMath', `exchangePricesAndConfig`) but that density is load-bearing for the target domain rather than wasteful.

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 2-optional-parameter, fully documented, read-only tool with no output schema, the description covers when to call but not what comes back — the decoded rate/utilization fields are exactly what an agent needs to know and are not in any structured field. Adequate to invoke, incomplete for interpreting results.

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%, with both parameters documented including defaults and the exclusiveMinimum constraint, so the baseline is 3. The description adds only loose framing — 'post-trade utilization' implicitly motivates simBorrowDelta — and does not explain units, whether the delta is added to current state, or what a non-USDC tokenAddress implies.

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 verb+resource pair (decode Fluid's 256-bit BigMath storage slots / simulate post-trade utilization) and scopes it to the Fluid protocol, which separates it from the sibling set (Morpho, Ethena, Sky, Euler, Pendle). It stops short of naming which sibling to use for adjacent protocols, but an agent can still pick it out by protocol and by the state-unpacking purpose.

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 leading clause gives three explicit trigger conditions: a user asking about Fluid USDC borrow/supply rates, needing to decode `exchangePricesAndConfig`, or wanting post-trade utilization simulation. There are no when-not conditions or named alternatives, so it is clear context without exclusivity.

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