Skip to main content
Glama

Company overview

company_overview
Read-only

Company overview (GET https://app.deepvalues.ai/api/v1/companies/{ticker}/overview, e.g. https://app.deepvalues.ai/api/v1/companies/AAPL/overview — 0.001 credits per call ($0.005 when paid per call over x402); works with no credentials up to 25 call(s)/day per address) Missing data? Call request_data.

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": "company_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYesThe real ticker symbol, e.g. AAPL; share classes as BRK.B or BRK-B. Substitute it into the path (/fundamentals/AAPL), never the literal {ticker}.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / ticker / description
      Added value: +"The real ticker symbol, e.g. AAPL; share classes as BRK.B or BRK-B. Substitute it into the path (/fundamentals/AAPL), never the literal {ticker}."
    • addedInput schema / properties / ticker / examples
      Added value: +[
      +  "AAPL"
      +]
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds genuinely useful behavior: billing rate (0.001 credits, $0.005 over x402) and an unauthenticated rate limit of 25 calls/day. That is solid added context, but it says nothing about response shape, freshness, or what happens on an unknown ticker.

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

Conciseness3/5

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

Purpose is front-loaded in the first phrase, which is good, but the parenthetical stacks the full URL, a duplicate example URL, pricing, and quota into one dense clause. The example URL largely repeats what the schema already demonstrates about substitution.

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?

With no output schema, the description should convey what an 'overview' returns, and it does not, leaving the agent to guess the payload. Pricing, quota, and the request_data fallback are covered well, so the gap is confined to return-value expectations.

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 coverage is 100% and the schema itself explains ticker format and path substitution, so the description need not carry parameter meaning. It only restates the path template with {ticker}, adding no syntax or edge-case detail beyond the schema (e.g. invalid or delisted tickers).

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?

Names a specific resource (company overview) tied to a concrete endpoint and ticker path, so an agent knows it retrieves profile-level data for one company. It stops short of saying what the overview actually contains (sector, description, key stats), which would fully separate it from siblings like fundamentals or brief.

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 practical selection context that most definitions omit: cost per call, credential-free quota of 25 calls/day, and an explicit fallback ('Missing data? Call request_data'). It does not contrast with fundamentals, brief, or companies_search, so the agent must infer when overview is preferred over those.

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