FinBridge

Portfolio Import History

get_portfolio_history

Read-onlyIdempotent

List the append-only portfolio snapshots recorded for this user. Each import_portfolio call that actually changes the stored holdings/assets (and each restore_portfolio_snapshot) appends one snapshot of the whole portfolio at that moment — quantities, average prices, symbols and asset classes, never market prices or computed valuations (those are recomputed fresh whenever needed). Identical resubmissions do not create a duplicate entry. Use this to see when the portfolio changed, then restore_portfolio_snapshot to undo a bad import.

Input Schema

Name	Required	Description	Default
`limit`	No	Max snapshots to return, most recent first. Default 20.

Output Schema

Name	Required	Description	Default
`count`	No
`error`	No
`snapshots`	No
`data_as_of`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedNov 4, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- changedOutput schema / properties / data_as_of / anyOf
```
Previous value: -[
-  {
-    "additionalProperties": true,
-    "properties": {},
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {},
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
```
- changedOutput schema / properties / snapshots / items / additionalProperties
```
Previous value: -trueNew value: +{}
```
- removedOutput schema / properties / snapshots / items / properties / assets_count / $ref
```
Removed value: -"#/properties/count"
```
- addedOutput schema / properties / snapshots / items / properties / assets_count / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / snapshots / items / properties / holdings_count / $ref
```
Removed value: -"#/properties/count"
```
- addedOutput schema / properties / snapshots / items / properties / holdings_count / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / snapshots / items / properties / id / $ref
```
Removed value: -"#/properties/count"
```
- addedOutput schema / properties / snapshots / items / properties / id / type
```
Added value: +[
+  "number",
+  "null"
+]
```

Changed1 schema field changedNov 2, 2026

addedOutput schema / properties / data_as_of

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

AddedSep 13, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive, so the bar is lower, yet the description adds substantive behavior: append-only semantics, exactly which operations trigger a snapshot (import_portfolio only when holdings actually change, plus restore_portfolio_snapshot), deduplication of identical resubmissions, and exclusion of computed market values. These are non-obvious traits an agent could not infer from annotations alone.

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?

Front-loaded with the core verb and resource, then layered with progressively finer behavioral detail; every sentence carries distinct information (trigger conditions, dedup rule, content exclusions, recommended use). No filler or restatement of the title.

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 an output schema present, return-value details needn't be described, and the definition covers the remaining gaps an agent would have: what creates entries, what they contain, what they omit, and how to act on them. Complete for a single-optional-parameter read tool.

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% and the single 'limit' parameter is fully documented in the schema (max 100, most recent first, default 20). The description adds no additional meaning about ordering, pagination, or the limit parameter, so the 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 and resource ('List the append-only portfolio snapshots') and immediately characterizes what a snapshot contains (quantities, average prices, symbols, asset classes) and what it never contains (market prices, valuations). This distinguishes it from get_portfolio, which returns current state, and from import/restore tools without needing their schemas.

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?

Explicitly says 'Use this to see when the portfolio changed, then restore_portfolio_snapshot to undo a bad import,' which names the follow-up action and the condition that motivates it. It doesn't explicitly say 'use get_portfolio instead when you want current holdings,' so the sibling exclusion for the read-current-state case is left implicit.

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.