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

@gblin-protocol/mcp-server

invest_usdc_to_gblin

Read-onlyIdempotent

Returns calldata to approve USDC and buy GBLIN, converting USDC into a cbBTC, WETH and USDC basket minted at NAV so agents can invest idle USDC on Base.

Instructions

Returns calldata that converts a USDC amount into GBLIN, a basket of cbBTC, WETH and USDC minted at NAV and redeemable at any time. Two steps: (1) approve USDC to the GBLIN Zap, (2) GBLINZap.buyGBLINWithToken, which swaps the USDC to WETH on Uniswap V3 and mints at NAV with a non-zero minimum output. Free. The mint fee and the yearly management fee are governance parameters read live from the vault, not fixed in this text.

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

Input Schema

NameRequiredDescriptionDefault
usdc_amountYesUSDC amount to invest (decimal string).
wallet_addressYesUser's wallet address that holds the USDC and signs the transactions.

Output Schema

NameRequiredDescriptionDefault
stepsYesTransactions to send in order.
actionYesAlways sequential_txs: send the steps one after the other.
expectedYesShares expected and the minimum applied.
gas_hintYesGas limit to set on the Zap step.
securityNo
gas_hint_noteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.1.5
    • addedInput schema / properties / wallet_address
      Added value: +{
      +  "description": "User's wallet address that holds the USDC and signs the transactions.",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "usdc_amount"
      -]New value: +[
      +  "usdc_amount",
      +  "wallet_address"
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "action": {
      +      "description": "Always sequential_txs: send the steps one after the other.",
      +      "type": "string"
      +    },
      +    "expected": {
      +      "description": "Shares expected and the minimum applied.",
      +      "type": "object"
      +    },
      +    "gas_hint": {
      +      "description": "Gas limit to set on the Zap step.",
      +      "type": "number"
      +    },
      +    "gas_hint_note": {
      +      "type": "string"
      +    },
      +    "security": {
      +      "type": "object"
      +    },
      +    "steps": {
      +      "description": "Transactions to send in order.",
      +      "items": {
      +        "description": "One transaction to send, in order: target, calldata, value in wei, and gas when the step needs an explicit limit. The same call is repeated as to, data and chainId (8453) for wallet batch APIs such as send_calls.",
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "action",
      +    "steps",
      +    "expected",
      +    "gas_hint"
      +  ],
      +  "type": "object"
      +}
  2. First observedv1.1.2

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, and the description is fully consistent, saying the tool returns calldata rather than executing. Beyond the annotations it adds real value: the Uniswap V3 swap-to-WETH route, the non-zero minimum output safeguard, and the warning that mint and management fees are governance parameters read live rather than fixed. It stops short of covering failure modes or approval-amount semantics.

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?

The core function is front-loaded in the first sentence, followed by the two-step mechanics and fee caveat. Four sentences with minimal waste, though the parenthetical basket definition and the fee disclaimer could be tightened slightly.

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?

An output schema exists, so return values need not be explained. Given that, the description covers everything an agent needs: what is produced, the two-step execution path, the swap venue, slippage protection, and the fact that fees are dynamic governance parameters. Nothing material is missing for a two-parameter read-only calldata builder.

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 both parameters are already documented and the baseline of 3 applies. The description adds only marginal context — that the USDC is swapped and the wallet is the signer — but does not clarify decimal precision, whether the amount is in base units, or approval-amount relationships.

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 opening sentence states a specific verb and resource — returns calldata converting USDC to GBLIN — and defines what GBLIN is (a basket of cbBTC, WETH, USDC). It clearly separates this from a plain swap by describing the NAV mint mechanism. It does not, however, distinguish itself from the reverse-direction sibling swap_gblin_to_usdc_jit, leaving that inference to the agent.

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 description gives a useful procedural breakdown (approve USDC, then call buyGBLINWithToken), which tells the agent how the returned calldata is meant to be used. But there is no explicit statement of when to prefer this over quote_safe_swap, preview_steps, or prepare_gblin_payment, and no exclusions or prerequisites. Usage is implied rather than directed.

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