Skip to main content
Glama

Get Trump Mentions Portfolio Holdings

get_trump_mentions_holdings
Read-onlyIdempotent

Get the latest live holdings for a portfolio tracking stocks mentioned by Donald Trump.

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

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of results per page (1–50, default 25)
cursorNoPagination cursor (offset)
sort_byNoField to sort by (default: total_value)
sort_dirNoSort direction (default: desc)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already establish read-only, idempotent, non-destructive, and closed-world behavior. The description adds useful context with 'latest live' freshness and portfolio scope, but it does not mention pagination behavior, rate limits, or the shape of returned holdings.

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?

The description is a single front-loaded sentence with no filler. Although 'latest live' is slightly redundant, every phrase contributes to identifying the dataset.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description identifies the dataset clearly enough for a simple read-only list tool, and annotations plus schema cover safety and parameters. However, it does not explain how this differs from close siblings or what a holding record contains, which matters given the dense sibling set and absence of an output schema.

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 limit, cursor, sort_by, and sort_dir are already fully documented in the input schema. The description adds no additional parameter meaning, defaults, or sorting guidance beyond what the schema provides.

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?

The description uses a specific verb and resource: getting holdings for a portfolio tracking stocks mentioned by Donald Trump. It distinguishes itself from performance-oriented siblings by returning holdings, but it does not explicitly differentiate itself from get_trump_holdings or get_trump_admin_holdings.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use this tool instead of get_trump_holdings, get_trump_mentions, or get_trump_mentions_performance. Usage is only implied by the resource description, with no exclusions or alternative routing.

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