Skip to main content
Glama

Get Trump's Sponsors Portfolio Holdings

get_trump_sponsors_holdings
Read-onlyIdempotent

Get the latest live holdings for a portfolio of public companies tied to Trump Accounts and the White House Ballroom fundraising drive. Use the portfolio param to pick the slice: 'all', 'trump-accounts', or 'ballroom'.

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

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of results per page (1–50, default 25)
cursorNoPagination cursor (offset)
searchNoCase-insensitive search over ticker and company name
sort_byNoField to sort by (default: position_size)
sort_dirNoSort direction (default: desc)
portfolioNoWhich sponsor portfolio to return (default: all)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds that data is 'latest live' (freshness expectation), which is genuinely useful, but it says nothing about pagination behavior despite limit/cursor params, nor about result volume or defaults.

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 tight sentences, zero redundancy, with the core capability stated first and the parameter selection rule immediately after. Every sentence earns its place.

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?

For an all-optional, annotated, read-only list tool with no output schema, the description covers what is returned at a high level ('latest live holdings'). It does not explain what a holding record contains (position size, weight, returns — only inferable from the sort_by enum), which is the one gap an agent might trip on.

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%, so the baseline is 3. The description's only parameter content is enumerating the 'portfolio' values, which the schema already lists; it does add a hint of what the slices mean topically (Trump Accounts, Ballroom), but gives no guidance on limit, cursor, search, or sort defaults.

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 ('Get the latest live holdings') and narrows scope to companies tied to Trump Accounts and the White House Ballroom fundraising drive, which distinguishes it from the numerous sibling holdings tools (get_trump_holdings, get_trump_admin_holdings, get_trump_mentions_holdings). It does not explicitly name a sibling or contrast itself against them, so it stops short of a 5.

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?

The second sentence tells the agent how to pick a slice of this tool's own data via 'portfolio', but there is no guidance on when to choose this tool over get_trump_holdings, get_trump_admin_holdings, or get_trump_mentions_holdings. Usage is implied by the sponsor/ballroom framing rather than stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources