fibx

Official

by Fibrous-Finance

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Cross-Chain Portfolio

get_portfolio

Read-only

Retrieve a complete cross-chain portfolio overview with USD valuations for token holdings across Base, HyperEVM, and Monad, including Aave V3 DeFi positions and total net worth.

Instructions

Get a complete cross-chain portfolio overview with USD valuations for all token holdings across Base, HyperEVM, and Monad. Includes DeFi positions (Aave V3). Returns total net worth.

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_portfolio"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 30, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds real scope context (which chains, that Aave V3 positions are folded in, that a net-worth total is returned) but says nothing about price freshness, per-chain partial-failure behavior, or latency — meaningful for a multi-chain aggregator.

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?

Three short sentences with zero waste; the cross-chain scope is front-loaded and the coverage details follow. Each sentence carries distinct information (scope, DeFi inclusion, return summary).

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?

With zero parameters and no output schema, the description carries the return-value burden and does name the headline contents: USD valuations, token holdings, DeFi positions, and total net worth. It stops short of describing the response shape or what happens when one chain is unreachable, which leaves a small gap for a multi-chain aggregation tool.

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. Nothing in the description misleads about inputs.

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 and resource ('Get a complete cross-chain portfolio overview') and scopes it to Base, HyperEVM, and Monad, plus DeFi positions via Aave V3. That chain enumeration implicitly separates it from get_balance and get_aave_status, though it never names those siblings outright.

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: an agent can infer this is the aggregate view versus get_balance (per-token balance) or get_aave_status (Aave-only). There is no explicit when-to-use, when-not-to-use, or reference to any alternative tool.

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