Skip to main content
Glama

Company snapshot

get_company
Read-only

Returns one company's current snapshot: price with its market session, performance, 52-week range, trend, fundamentals from its SEC filings, balance sheet (cash, debt as filed, financings since, runway, share count), risk (beta, volatility), FINRA short interest, and its SEC profile with its own description: every figure with the date it holds for. Use it when the user asks about one company's price, market cap, valuation, fundamentals or risk. A pre-IPO company (e.g. 'anthropic') returns what its prospectus and the funds file instead: no price, the last round's price per common share and the implied value on both share counts.

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": {
      "symbol": "<symbol>"
    },
    "name": "get_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesTicker or company name, e.g. NVDA, AMD, ASML, 'nvidia', 'taiwan semiconductor'. Case-insensitive.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare readOnly/openWorld=false, and the description adds materially beyond them: every figure carries the date it holds for, and the pre-IPO path is spelled out (no price, last round's price per common share, implied value on both share counts, prospectus and fund filings instead). That fallback semantics is non-obvious and directly changes how an agent interprets the result.

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

Conciseness4/5

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

Front-loaded with the resource and its contents, then the usage rule, then the edge case — a sensible order. The long inventory of fields is dense but each item maps to a real return category, so it earns its place; a minor trim is possible in the fundamentals/balance-sheet phrasing.

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?

No output schema exists, so the description must carry return semantics, and it does: it names the payload categories, the per-figure as-of dating, and the pre-IPO branch. The one gap is failure behavior for an unresolvable symbol (unknown company), which an agent would want before calling.

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?

With one parameter at 100% schema coverage, the schema already documents that symbol accepts a ticker or company name, case-insensitive. The description's mention of 'anthropic' and the pre-IPO path adds a little behavioral color about accepted inputs but no new syntax or constraints. This is the baseline-3 case where 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 specific verb and resource ('Returns one company's current snapshot') and then enumerates the exact contents: price/session, performance, 52-week range, fundamentals, balance sheet, risk, short interest, SEC profile. That enumeration implicitly separates it from siblings like get_financials, get_price_history, and compare_companies, which cover only slices or multiples of companies.

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

Usage Guidelines4/5

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

Gives an explicit trigger: 'Use it when the user asks about one company's price, market cap, valuation, fundamentals or risk.' That is clear context, but it names no alternatives and no exclusions, even though get_financials, get_price_history, and compare_companies overlap heavily. An agent still has to infer when the narrower siblings are preferable.

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.