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

@gblin-protocol/mcp-server

get_treasury_state

Read-onlyIdempotent

Read the current GBLIN protocol state on Base mainnet, including NAV in USD, basket composition, Crash Shield status, and NAV reliability.

Instructions

Reads the current GBLIN protocol state on Base mainnet: NAV in USD, basket composition with dynamic weights, Crash Shield status and whether the NAV is reliable.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
metaNo
basketYesAssets in the basket with base and dynamic weights.
nav_usdYesNet asset value of one GBLIN share in USD.
auction_openYesTrue while a rebalancing auction is running.
nav_reliableYesFalse when a price feed is stale or a basket asset cannot be read; do not trade on the NAV then.
eth_price_usdYesETH price in USD from the oracle.
slippage_reasonNo
crash_shield_activeYesTrue when the crash shield has cut the weight of a falling asset.
slippage_buffer_pctNo
management_fee_bps_per_yearYesManagement fee in basis points per year, read from the contract.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.1.5
    • addedInput schema / required
      Added value: +[]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "auction_open": {
      +      "description": "True while a rebalancing auction is running.",
      +      "type": "boolean"
      +    },
      +    "basket": {
      +      "description": "Assets in the basket with base and dynamic weights.",
      +      "items": {
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "crash_shield_active": {
      +      "description": "True when the crash shield has cut the weight of a falling asset.",
      +      "type": "boolean"
      +    },
      +    "eth_price_usd": {
      +      "description": "ETH price in USD from the oracle.",
      +      "type": "number"
      +    },
      +    "management_fee_bps_per_year": {
      +      "description": "Management fee in basis points per year, read from the contract.",
      +      "type": "number"
      +    },
      +    "meta": {
      +      "type": "object"
      +    },
      +    "nav_reliable": {
      +      "description": "False when a price feed is stale or a basket asset cannot be read; do not trade on the NAV then.",
      +      "type": "boolean"
      +    },
      +    "nav_usd": {
      +      "description": "Net asset value of one GBLIN share in USD.",
      +      "type": "number"
      +    },
      +    "slippage_buffer_pct": {
      +      "type": "number"
      +    },
      +    "slippage_reason": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "nav_usd",
      +    "eth_price_usd",
      +    "nav_reliable",
      +    "management_fee_bps_per_year",
      +    "auction_open",
      +    "crash_shield_active",
      +    "basket"
      +  ],
      +  "type": "object"
      +}
  2. First observedv1.1.2

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so the safety profile is covered. The description adds one genuinely useful detail beyond that: 'whether the NAV is reliable', signaling that the returned NAV can be stale or untrustworthy. It stops short of saying why the NAV might be unreliable or whether the read is live on-chain vs cached.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with the verb and scope first, followed by the concrete data points returned. No filler, no restatement of the tool name, every clause carries information.

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

Completeness4/5

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

An output schema exists, so return shape need not be re-explained, and annotations carry the safety profile; the description's enumeration of state components is sufficient to decide to call it. Minor gap: freshness/latency and what makes the NAV unreliable flag flip are not addressed, which matters for a live-state read.

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?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly avoids inventing input discussion.

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 ('Reads') and resource ('current GBLIN protocol state on Base mainnet') and enumerates the returned fields: NAV in USD, basket composition with dynamic weights, Crash Shield status, NAV reliability. However, it never distinguishes itself from close siblings like analyze_treasury_health and get_nav_history, leaving the agent to infer the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance, and no alternatives are named. With overlapping siblings (analyze_treasury_health, get_nav_history, get_auction_state) present, the description gives the agent nothing to route on beyond the tool's own subject matter.

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