fund_holdingsA fund's current portfolio positions with quarter-over-quarter change.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Fund slug (URL identifier). |
| Name | Required | Description | Default |
|---|---|---|---|
| fund | Yes | ||
| quarter | Yes | ||
| holdings | Yes | ||
| provenance | Yes | ||
| total_value | Yes |
Changes observed during successful MCP inspections.
Output schema / properties / holdings / items / properties / security / properties / listingAdded value: +{
+ "anyOf": [
+ {
+ "additionalProperties": false,
+ "properties": {
+ "disclosure_note": {
+ "type": "string"
+ },
+ "event_type": {
+ "enum": [
+ "ipo",
+ "direct_listing",
+ "spin_off"
+ ],
+ "type": "string"
+ },
+ "listed_on": {
+ "format": "date",
+ "type": "string"
+ },
+ "recently_listed": {
+ "type": "boolean"
+ },
+ "source_url": {
+ "format": "uri",
+ "type": "string"
+ }
+ },
+ "required": [
+ "listed_on",
+ "event_type",
+ "recently_listed",
+ "source_url",
+ "disclosure_note"
+ ],
+ "type": "object"
+ },
+ {
+ "type": "null"
+ }
+ ]
+}Output schema / properties / holdings / items / properties / security / requiredPrevious value: -[
- "ticker",
- "name"
-]New value: +[
+ "ticker",
+ "name",
+ "listing"
+]Output schema / properties / holdings / items / properties / position_typeAdded value: +{
+ "enum": [
+ "direct",
+ "call",
+ "put"
+ ],
+ "type": "string"
+}Output schema / properties / holdings / items / requiredPrevious value: -[
- "security",
- "shares",
- "value",
- "percent_of_fund",
- "change",
- "change_percent"
-]New value: +[
+ "security",
+ "position_type",
+ "shares",
+ "value",
+ "percent_of_fund",
+ "change",
+ "change_percent"
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds no behavioral details but is consistent with annotations, so the lower bar is met and no contradictions exist.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, concise sentence with no extraneous words. It efficiently conveys the tool's purpose without redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the simple nature of the tool and the presence of an output schema, the description is complete. It does not need to explain return values, and it provides enough context for callers.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The single parameter 'slug' is described as 'Fund slug (URL identifier)', which is clear and covers the schema fully. Though minimal, it provides sufficient meaning for a unique identifier.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool provides current portfolio positions with quarter-over-quarter change. It distinguishes from siblings like fund_history (historical data) and get_fund (general fund info) by focusing on holdings and their changes.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description offers no explicit guidance on when to use this tool versus alternatives. It implies usage for current holdings but does not contrast with siblings or state conditions for selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.