Talval

Get a superinvestor's portfolio

get_superinvestor

Read-onlyIdempotent

One tracked investor's reported holdings and quarter-on-quarter activity. Call list_superinvestors first to get the slug.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	Yes	Slug, e.g. 'berkshire'.

Output Schema

TableJSON Schema

Name	Required	Description
`slug`	Yes
`found`	Yes	False when no tracked investor has that slug.
`person`	No
`manager`	No
`activity`	No	Quarter on quarter. Null when there is no prior filing to compare against.
`holdings`	No	Largest first, capped at 30.
`n_positions`	No
`quarter_end`	No
`portfolio_value_usd`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 29, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "activity": {
+      "description": "Quarter on quarter. Null when there is no prior filing to compare against.",
+      "properties": {
+        "added_to": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "new_buys": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "reduced": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "sold_out": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        }
+      },
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "found": {
+      "description": "False when no tracked investor has that slug.",
+      "type": "boolean"
+    },
+    "holdings": {
+      "description": "Largest first, capped at 30.",
+      "items": {
+        "properties": {
+          "activity": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "issuer": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "pct_of_portfolio": {
+            "description": "Percent, e.g. 12.4.",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "ticker": {
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "manager": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "n_positions": {
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "person": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "portfolio_value_usd": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "quarter_end": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "slug": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "slug",
+    "found"
+  ],
+  "type": "object"
+}

First observedSep 21, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is fully covered. The description adds the quarter-on-quarter activity framing and the sibling dependency, but says nothing about rate limits or staleness despite the name 'reported holdings' implying a reporting lag.

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?

Two sentences, zero waste. The resource description is front-loaded and the prerequisite call is the second sentence, which is the right order.

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?

Single-parameter read tool with a full annotation set and an output schema, so the agent has what it needs to call it correctly. The remaining gap is that 'reported holdings' and 'quarter-on-quarter activity' are not anchored to which quarter or what reporting lag to expect.

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 even gives an example slug ('berkshire'). The description adds no format or syntax detail beyond what the schema provides, so the baseline 3 applies.

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+resource: fetches one tracked investor's reported holdings and quarter-over-quarter activity. Distinguishes it from the sibling list_superinvestors by naming that tool as the prerequisite. Could be sharper about what 'activity' means, but the scope is clear.

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 tells the agent to call list_superinvestors first to obtain the slug, and the shared noun 'superinvestor' ties this tool to its sibling. The one condition that matters for correct invocation is stated.

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

All Talval 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.

Resources

Need Help?