Skip to main content
Glama
@gblin-protocol/mcp-server

@gblin-protocol/mcp-server

plan_treasury

Read-onlyIdempotent

Turns idle USDC into a reviewable treasury plan: calculates operating cash and surplus, simulates GBLIN minting at NAV with fees and exit costs, and flags blockers. Read-only; nothing is executed.

Instructions

Turns idle USDC into a reviewable plan in one call: operating cash = max(reserve_usd, daily_burn_usd x days), the surplus above it, a simulation of minting that surplus into GBLIN at NAV (fees read live from the vault, estimated exit value today, round-trip cost), the same simulation for a trial amount (100 USDC by default), and the blockers (Crash Shield, redemption cooldown, ETH for the exit). Read-only: nothing is executed and nothing is advised. GBLIN is crypto exposure (cbBTC, WETH, USDC), not cash and not yield.

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": {
      "wallet_address": "<wallet_address>"
    },
    "name": "plan_treasury"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoDays of spend to keep liquid (default 7, max 365).
trial_usdcNoTrial amount to simulate beside the surplus (default 100).
reserve_usdNoUSD to keep liquid regardless of the burn rate; the larger of the two rules wins.
daily_burn_usdNoAverage daily spend in USD. Operating cash = daily_burn_usd × days.
wallet_addressYesAgent's 0x address.

Output Schema

NameRequiredDescriptionDefault
nextYesThe tools to call after a human confirms.
as_ofNoBlock and time the reads were taken at.
notesNo
trialYesThe same simulation for the trial amount.
inputsNoThe inputs as applied, with the defaults filled in.
marketYesNAV, ETH price, risk regime and crash shield status.
walletYes
surplusYesUSDC above the operating cash.
blockersYesReasons parking is not appropriate right now, if any.
simulationYesMint simulation for the surplus: shares, fees, exit value today, round-trip cost; or nothing_to_park.
wallet_stateYesUSDC, GBLIN and ETH balances, gas health, redemption cooldown.
operating_cashYesUSDC to keep liquid: max(reserve_usd, daily_burn_usd × days), with the runway in days.
park_candidateYesTrue when no blocker applies. Not a recommendation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.5

TDQS

A4.4/5.0
Behavior5/5

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

Goes well past the annotations: it gives the operating-cash formula, names the simulation components (vault-live fees, estimated exit value, round-trip cost), and lists concrete blockers (Crash Shield, redemption cooldown, ETH for the exit). Annotations only say readOnly/idempotent; the description adds the mechanics an agent needs, plus a risk disclaimer that GBLIN is crypto exposure, not cash or yield.

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?

Front-loaded with the verb and result, and every clause carries information - formula, simulation contents, blockers, read-only status, risk caveat. However it is one dense, run-on sentence of roughly 80 words; splitting it into two or three would aid scanning without losing content.

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

Completeness5/5

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

For a read-only, open-world planning tool with an output schema and full annotation coverage, this is complete: it says what is computed, what the plan contains, what can block it, and that nothing executes or is advised. Return-value shape is covered by the output schema, so no further detail is owed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds the derivation the schema cannot express: operating cash = max(reserve_usd, daily_burn_usd x days), which explains how the two optional params interact and which wins. It also restates the trial-amount default. Incremental value over the schema is real, though modest.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('turns idle USDC into a reviewable plan in one call') and enumerates the plan's contents, so the agent knows exactly what it gets back. The closing contrast with execution tools ('nothing is executed') separates it from invest_usdc_to_gblin and swap_gblin_to_usdc_jit without needing to open their schemas.

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 implied rather than stated: 'reviewable plan' plus 'read-only, nothing executed' signals this is the pre-flight step before an execution sibling, but no sibling is named as the alternative. There is also no explicit statement of when not to use it (e.g. for wallets with no USDC, or when only a quote is wanted).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.