Skip to main content
Glama
Sign In

ticker-scout

by ai.tickerscout
OverviewDiscussionsAdmin

Headline figures and summary for the latest period

get_key_figures
Read-onlyIdempotent

The headline for a company's most recent reported period: revenue, net income, diluted EPS and similar, each with its exact dollar amount, prior-year value, year-over-year change, the record field it was read from and its SEC accession number; plus a one-paragraph written summary and question-and-answer pairs built from those figures. Start here for any 'how did X do' or 'how much did X earn' question. Far smaller than get_financials. Pass record for an earlier record's headline. For any other figure, or a figure across periods, use get_figure.

Input Schema

NameRequiredDescriptionDefault
recordNoAn earlier published record, by tag ('FY27Q1') or by the period its filing reports ('Q1 FY2027'). Omit for the latest. list_periods lists every record.
tickerYesTicker symbol, case-insensitive. Examples: NVDA, brk-b, BRK.B.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / record
      Added value: +{
+  "description": "An earlier published record, by tag ('FY27Q1') or by the period its filing reports ('Q1 FY2027'). Omit for the latest. list_periods lists every record.",
+  "type": "string"
+}
    • changedInput schema / properties / ticker / description
      Previous value: -"Ticker symbol, case-insensitive. Examples: NVDA, brk-b."New value: +"Ticker symbol, case-insensitive. Examples: NVDA, brk-b, BRK.B."
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds value beyond that by disclosing the payload shape (figures plus prose summary plus Q&A) and a relative cost signal ('Far smaller than get_financials'), which is genuinely useful for context budgeting. It stops short of mentioning auth, rate limits, or pagination, so not a 5.

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?

Front-loaded with the return contents, then the routing rule, then the fallback sibling. The enumeration is dense but every element earns its place, and no sentence is wasted or redundant with the schema.

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

Completeness5/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 full burden of describing returns, and it does so thoroughly (fields, prior-year comparison, provenance via accession number, plus summary and Q&A). Combined with the explicit sibling routing, an agent has everything needed to call this correctly.

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%, and both parameters are fully documented there, including tag formats for record and ticker casing examples. The description only restates the record behavior ('Pass record for an earlier record's headline') without adding syntax or edge-case meaning. Baseline 3 when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete resource (headline figures for the most recent reported period) and enumerates exactly what comes back: revenue, net income, diluted EPS, prior-year value, YoY change, source record field, SEC accession number, plus a written summary and Q&A pairs. It also distinguishes itself from siblings by name (get_financials, get_figure), so an agent can route without opening any schema.

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

Usage Guidelines5/5

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

Explicit when-to-use ('Start here for any how did X do or how much did X earn question') and explicit when-not-with-alternative ('For any other figure, or a figure across periods, use get_figure'). It also covers the earlier-period case via the record parameter, leaving nothing to inference.

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

All ticker-scout toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources