FinBridge

My Portfolio

get_portfolio

Read-only

Return the holdings this user has already registered in FinBridge with import_portfolio — listed stocks plus cash, crypto, ETF and physical assets — valued at the latest prices, with return and asset allocation. A user who has registered nothing gets an empty list.

Not this tool for: analysing or valuing a company (get_valuation), prices (get_stock_prices), or finding companies (search_dart_company / search_edgar_company). It reads only what this user stored, so it knows nothing about a company they do not hold.

Crypto and ETFs use live ccxt quotes, stocks the latest close in the database, cash and physical assets the registered amount. allocation is aggregated per currency; combined converts everything to KRW using an ECB-derived USD/KRW rate.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	No
`error`	No
`notes`	No
`combined`	No
`holdings`	No
`allocation`	No
`total_value`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 7, 2026

addedOutput schema / properties / combined

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "properties": {},
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

First observedSep 6, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Goes far beyond the readOnly/openWorld/destructive annotations by disclosing valuation sources (live ccxt for crypto/ETFs, latest database close for stocks, registered amounts for cash/physical), currency aggregation behavior, and KRW conversion method. It also documents empty-list behavior and the tool's ignorance of unheld companies.

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?

Every sentence carries useful information: purpose, exclusions, empty behavior, data freshness, and currency handling. Despite the length, it is tightly organized and front-loaded with the core definition.

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?

Covers all non-obvious aspects an agent needs: input-less scope, return composition, valuation rules, currency conversion, empty result behavior, and explicit sibling routing. With an output schema present and zero parameters, nothing essential 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?

The input schema has zero parameters, so there is nothing to document. The description still adds meaningful context about the implicit scope (the current user's registered holdings), which is the closest analog to parameter semantics.

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 ('Return') and resource (holdings registered in FinBridge via import_portfolio), and enumerates the asset classes covered. It names sibling exclusions (get_valuation, get_stock_prices, search_dart_company / search_edgar_company) so the agent can disambiguate.

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

Usage Guidelines5/5

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

Explicitly says when not to use the tool and names the relevant alternatives: valuation, prices, and company search. Also clarifies that it only reflects the current user's stored holdings, which prevents misuse for general market/screening queries.

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

All FinBridge tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.