Skip to main content
Glama

Get recent news and updates on a stock

get_stock_updates
Read-only

Recent events for a covered US stock (earnings, filings, analyst rating changes, material news), each explained in plain English with why it matters for a long-term owner and links to the primary source.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ticker": "<ticker>"
    },
    "name": "get_stock_updates"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many recent updates to return (default 8)
tickerYesStock ticker symbol, for example NVDA or BRK-B

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description adds genuinely new context: the output is narrated "in plain English with why it matters for a long-term owner" plus links to primary sources, and it is limited to US names. It does not define the recency window or say what happens for an uncovered ticker.

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?

One well-formed sentence, front-loaded with the resource and scope, then the event types, then the value-add of the output. No filler or restatement of the title.

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 a simple read-only, two-parameter tool with no output schema, describing the returned content (explanation, rationale, source links) covers most of what an agent needs. The gaps are the recency definition and the uncovered-ticker behavior, both minor given the annotations.

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%, so the baseline is 3, but the description adds a real constraint beyond the schema: the ticker must belong to a covered US stock, which the schema's generic 'stock ticker symbol' does not convey. It says nothing extra about limit, which the schema already documents.

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?

Specific verb+resource with a clear scope: "Recent events for a covered US stock," and an enumeration of event classes (earnings, filings, analyst rating changes, material news). It does not explicitly contrast itself with siblings like get_stock_thesis, though the 'recent events' framing is naturally distinct from a thesis or a listing tool.

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 word "covered" implies a precondition (the ticker must be in coverage), but the description never states when to use this versus get_stock_thesis or how to check coverage via list_covered_stocks. Usage is implied rather than instructed.

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