Skip to main content
Glama
Sign In
fibx

fibx

Official
by Fibrous-Finance
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Open FibX

open_fibx
Read-onlyIdempotent

Open the FibX app to view wallet balances, signing policy, and a quoted swap form in one snapshot; optionally pre-fill a Fibrous quote with token amounts and chain. No transaction is executed.

Instructions

Open the FibX app: wallet, balances, signing policy, and a swap form with the Fibrous route. Call this FIRST for anything about the wallet, a balance, a quote, or a swap — it returns the session, balances, policy and quote in one snapshot, so get_auth_status, get_balance, get_policy and get_quote are not needed before it. It executes nothing; where the host renders MCP Apps UI the user sees the app and presses Simulate and Swap themselves. Pass from/to/amount to open it pre-filled with a quote. Supported chains: Base, HyperEVM, Monad. If the host does not render UI, the result is still a complete JSON snapshot you can read and summarise.

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

Input Schema

NameRequiredDescriptionDefault
toNoDestination token symbol, to pre-fill a swap
fromNoSource token symbol, to pre-fill a swap
chainNoChain to open onbase
amountNoAmount of the source token, to pre-fill a swap
slippageNoSlippage percent for the pre-filled quote

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.10.2

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive, open-world), the description discloses the key behaviors an agent could not otherwise know: nothing is executed, the human presses Simulate and Swap in rendered MCP Apps UI, and the pre-fill behavior via from/to/amount. It also covers the non-UI fallback (a complete JSON snapshot the agent can read and summarize) and pins the supported chains.

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?

It is front-loaded with the call-FIRST routing rule, then the non-execution caveat, then the pre-fill mechanics, then the no-UI fallback — a sensible order of decision-critical information. Every sentence carries information an agent needs; there is no restatement of the title or filler.

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?

With five optional params and no output schema, the description carries the full burden and meets it: it states what the snapshot contains (session, balances, policy, quote), how behavior differs across UI and non-UI hosts, and that all params are optional pre-fill hints. Nothing required to invoke it correctly is missing.

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 real meaning by grouping from/to/amount into a single intent: they open the app pre-filled with a quote, not just three independent strings. It also reiterates the chain constraint (Base, HyperEVM, Monad) and implies slippage applies to the pre-filled quote, though slippage itself is never mentioned by name.

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?

The description opens with a specific verb and resource ("Open the FibX app") and enumerates exactly what the app surfaces: wallet, balances, signing policy, and a swap form with a Fibrous route. It then explicitly distinguishes itself from get_auth_status, get_balance, get_policy and get_quote, so an agent can choose it over those siblings without reading any schema.

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?

It gives an explicit directive ("Call this FIRST for anything about the wallet, a balance, a quote, or a swap") and names the four sibling tools it obviates, which is unusually strong routing guidance. The gap is that it never names swap_tokens as the execution path — the agent must infer from "It executes nothing" that actual swaps go elsewhere.

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