Skip to main content
Glama
tearsheet

tearsheet

by kewonit

company_snapshot

Read-only

Retrieve a one-call overview of a listed Indian company, covering identifiers, price, market cap, valuation ratios, key metrics, multi-year averages, dividends, and dated events for general research.

Instructions

Get a one-call overview of a listed Indian company.

    Returns identifiers, status, size class, delayed price, market cap, P/E,
    PEG, key ratios with their units, multi-year ROE and margin averages,
    price changes up to one year, recent dividends and dated key events.
    Use it first when asked about a company in general. It contains facts
    only: Tijori's own opinions and forecasts are deliberately left out.
    Longer-term returns are omitted because their basis isn't stated.
    

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": {
      "company": "<company>"
    },
    "name": "company_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyYes

Output Schema

NameRequiredDescriptionDefault
dataYes
as_ofNo
unitsNo
entityNo
sourcesNo
warningsNo
next_cursorNo
retrieved_atNo
verificationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior5/5

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

Beyond readOnlyHint the description discloses real provenance caveats: the price is delayed, opinions and forecasts are deliberately excluded, and longer-term returns are omitted because their basis isn't stated. Those are exactly the facts an agent needs in order to trust and bound the answer, and they cannot be inferred from the annotations or output schema.

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: the verb-and-resource sentence comes first, then returns, then usage, then caveats. Two sentences are spent on exclusions, which is slightly more than strictly necessary, but both carry decision-relevant information rather than filler.

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?

An output schema exists and the tool takes one parameter, so the description is nearly complete; the enumerated return contents and the deliberate omissions round it out. The only meaningful hole is the unresolved input identifier format, which matters because the agent must supply it on the first call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the single parameter is undocumented, so the description carries the full burden. It only implies a company is involved and says "listed Indian" in scope, without stating whether the value is a ticker, legal name, or Tijori identifier, or how ambiguous matches are handled.

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?

"Get a one-call overview of a listed Indian company" pairs a specific verb with a specific resource and scope, then enumerates the contents (identifiers, status, price, P/E, PEG, ratios, ROE, margins, dividends, events). That enumeration is what separates it from the single-slice siblings such as get_financials or get_ownership without naming them.

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?

"Use it first when asked about a company in general" gives a clear entry-point rule and implicitly tells the agent to reach for the snapshot before drilling into narrower tools. It stops short of naming any alternative or stating when a sibling is preferable, so it falls below the 5 bar.

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