Skip to main content
Glama
screener-mcp
by LogeshR15

get_company_overview

Read-only

Retrieve a company's key ratios, current price with freshness details, 52-week range, and about section to start equity analysis.

Instructions

Get a company's key ratios, current price, 52-week range, and about section.

data.price_freshness says when the price is from (price_as_of), whether it's an intraday print or the last close, the previous close and the day's change — so you can tell how current "current_price" is.

symbol: NSE/BSE symbol (e.g., "TCS", "INFY", "RELIANCE", "HDFCBANK") financial_type: "consolidated" (default) or "standalone"

This is the best starting point for any company analysis.

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

Input Schema

NameRequiredDescriptionDefault
symbolYes
financial_typeNoconsolidated

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint true, openWorldHint true), so the description is not obligated to explain side effects. It does add non-obvious behavioral context by pointing at data.price_freshness and explaining what price_as_of, intraday-vs-close, previous close and day change mean, which tells the agent how much to trust the price. It omits any note on latency or symbol-universe restrictions.

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?

The lead sentence names the payload, then the freshness paragraph, then per-parameter lines, then a positioning line – a clean front-loaded structure. The freshness block is the longest part but each clause maps to a distinct field, so little is wasted. Minor redundancy with the output schema keeps it from a 5.

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?

For a simple two-parameter read tool with an output schema and read-only annotations, the description covers purpose, both parameters, output-freshness semantics, and a positioning statement. An agent has everything needed to select and call it correctly without consulting the schema.

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 description coverage is 0%, so the description carries the full burden and largely meets it: symbol is explained as an NSE/BSE code with four concrete examples, and financial_type is given its two accepted values with the default called out. It does not state what happens if an unrecognized symbol or financial_type is passed. Strong compensation for an undocumented schema.

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 a specific verb and enumerates the resources returned: key ratios, current price, 52-week range, and about section. That is far more informative than a restated title. It does not name a specific sibling it displaces, relying instead on the loose claim of being the 'best starting point', so it stops short of a 5.

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?

'This is the best starting point for any company analysis' gives an implied entry point for the tool family, which is real but weak guidance. There is no when-not-to-use condition and no sibling is named as the alternative for deeper data (e.g. get_financials, get_full_analysis). Usage is inferable rather than stated.

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