Skip to main content
Glama

Nvidia Hub: live Nvidia, where the AI money goes when Nvidia is sold, earnings, options and AI spending

get_nvidia
Read-only

The OwlChart Nvidia Hub in one tool (v5.896): what=market (NVDA price, change against yesterday's close, day range, pre market or after hours price, the highest trade, 7 day, 30 day and 1 year moves, market value, market open or closed, the next results date), brief (the facts, a plain read, the headline, the AI crypto verdict, the open risk stories), rotation (days=90 or 30: for the chip stocks, big tech, chip and tech funds, defensive funds, T-bill funds, gold, the dollar, Bitcoin, Ether and the AI tokens CARV, FET, TAO, VIRTUAL and their basket: today's move, the average move and on how many days it went up on the days Nvidia fell 2% or more, a plain label RECEIVING, SOLD WITH NVIDIA or NEUTRAL, the 30 and 90 day correlation word, today's ranked receivers and the markets sold together), verdict (is Nvidia money reaching the AI tokens: NOT RECEIVING, STARTING or RECEIVING with a 0 to 100 gauge, each sign and the history by day), hourly (Nvidia, AMD, Broadcom, SMH, the AI token basket and Bitcoin as percent from the open, hour by hour, and the hour the tokens split from Nvidia), news (Nvidia headlines with the share price move in the 60 minutes after each, and the risk strip), insiders (SEC Form 4 trades of the last 10 days), options (call and put volume, put to call ratio, 30 day implied volatility, biggest strikes, the implied move into the results; Cboe delayed quotes), supply-chain (capital spending of Microsoft, Alphabet, Amazon and Meta by quarter from SEC filings, accelerating or slowing), earnings (the last 8 quarters: revenue, data center revenue, gross margin, the beat or miss against Nvidia's own guidance range, the next day move, the live guidance) or crypto (correlation of each AI token with Nvidia over 30 and 90 days and the basket priced in Nvidia shares). v5.898: carv (CARV, the AI token that follows Nvidia most closely: the 30 and 90 day link and beta, every day Nvidia moved 3% or more with CARV the same day and the next, CARV the day after each results report, and whether CARV moved the same way as Nvidia between its close and its next open), fundamentals (from Nvidia's own SEC filings and the live price: revenue, growth, gross, operating and net margin, earnings per share, cash left after investment, return on equity and assets, cash, debt, price to earnings, price to sales, enterprise value to EBITDA) or comps (the same sums for AMD, Broadcom, Qualcomm, Micron and Intel). Analyst targets are not shown: no raw source publishes them. Moving together is not proof that money moved from one market to the other. Data, not advice. Page: https://owlchart.com/nvidia.html

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

Input Schema

NameRequiredDescriptionDefault
daysNorotation: the window in days, default 90
whatNowhich Nvidia data set, default brief

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already supply readOnlyHint=true and openWorldHint=true, so the safety profile is covered; the description adds meaningful context beyond that, notably 'Cboe delayed quotes' for the options data, 'Analyst targets are not shown', 'Moving together is not proof that money moved', and 'Data, not advice'. It does not mention staleness/caching or rate limits, keeping it below the top band.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core content is delivered as one enormous run-on sentence with deeply nested parenthetical lists, which is hard to scan and front-loads version numbers ('v5.896', 'v5.898') that add little for an agent. The information is relevant, but the packaging is far from concise or well structured.

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?

With no output schema, the description carries the burden of describing return content, and it does so thoroughly for every dataset option. Gaps are minor: no mention of response size, pagination, or failure modes for a large multi-dataset read tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with both parameters enum-described, so the baseline is 3; the description goes further by spelling out what each 'what' value actually returns (e.g. rotation's 30/90-day correlation and RECEIVING/SOLD WITH NVIDIA labels, fundamentals' SEC-sourced metrics). It clarifies the 'days' window only in passing ('days=90 or 30').

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 opens with 'The OwlChart Nvidia Hub in one tool' and then enumerates the fourteen datasets (market, brief, rotation, verdict, hourly, news, insiders, options, supply-chain, earnings, crypto, carv, fundamentals, comps) it can return, so the verb+resource is unambiguous. It does not differentiate itself from close siblings such as get_carv or get_news, even though 'carv' and 'news' are also enumerated here, leaving overlap unresolved.

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?

Usage is only implied: the agent must infer which 'what' value to pick from the enumerated contents, and the defaults ('default brief', 'days default 90') are stated. There is no explicit when-to-use-this-vs-sibling guidance and no when-not guidance, despite an obvious overlap with get_carv.

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