Skip to main content
Glama
Sign In
fibx

fibx

Official
by Fibrous-Finance
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Manage RPC Configuration

config_action

Manage fibx RPC settings: set a custom RPC URL per chain to avoid rate limits, view current RPCs, reset chains to defaults, or list custom settings.

Instructions

View and modify fibx RPC configuration. Use 'set-rpc' to set a custom RPC URL for a chain (helps avoid rate limits), 'get-rpc' to view the current RPC for a chain, 'reset-rpc' to reset a chain's RPC to default (omit chain to reset all), or 'list' to show all custom RPC settings.

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": {
      "action": "<action>"
    },
    "name": "config_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoRPC URL to set (required for set-rpc)
chainNoTarget chain (required for set-rpc and get-rpc)
actionYesConfig action to perform

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.10.2
    • changedInput schema / properties / chain / enum
      Previous value: -[
-  "base",
-  "citrea",
-  "hyperevm",
-  "monad"
-]New value: +[
+  "base",
+  "hyperevm",
+  "monad"
+]
  2. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations declare a non-read-only, non-destructive, closed-world operation; the description adds real behavioral context by explaining the motivation for set-rpc (rate limits) and the scope of reset-rpc, including that omitting chain wipes all custom settings — a meaningful side effect the annotations do not convey. It does not describe persistence, validation of the URL, or what a reset actually returns, which keeps it from a 5.

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 front-loaded sentence that leads with the purpose before listing actions, with no filler. It is dense and long-ish, but each clause maps to a distinct action or behavior, so nothing is wasted.

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?

For a three-parameter config tool with no output schema and full schema coverage, the description covers every action and its key side effect. Missing pieces are secondary: whether configuration changes persist, whether auth is needed, and whether reset-rpc's chain omission is easily reversible.

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%, and the schema already states that url is required for set-rpc and chain for set-rpc/get-rpc, so most of the description's parameter guidance is restated. The one genuine addition is the omission semantics for reset-rpc (omit chain to reset all), which is not derivable from the schema. Baseline 3 applies.

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+resource ("View and modify fibx RPC configuration") and then enumerates the four exact operations. The scope is clearly configuration management, which separates it cleanly from siblings like swap_tokens, get_balance, or set_policy_rule.

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?

Each action is bound to a concrete intent: set-rpc to avoid rate limits, get-rpc to inspect, reset-rpc to restore defaults, list to enumerate. It even covers the whole-configuration reset case. It stops short of stating prerequisites (e.g., wallet/auth requirements) or when not to use it, so it is strong but not exhaustive.

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