Skip to main content
Glama

SN Data by Shikshan Nivesh

Company and latest figures

get_company
Read-onlyIdempotent

One company's identity (name, exchange, industry, CIK) and its latest reported figures: trailing twelve months, latest quarter and year, margins, cash flow, balance sheet, share count. Also how many rows each dataset holds for it.

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

Input Schema

NameRequiredDescriptionDefault
tickerYesThe company's ticker, like AAPL. BRK.B and BRK-B both work.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety and repeatability are covered without prose. The description adds genuine content context beyond that: it spells out the breadth of the snapshot (TTM, latest quarter, latest year, margins, cash flow, balance sheet, share count) and the unusual inclusion of per-dataset row counts. It does not discuss result size or how missing/empty datasets are represented, which keeps it below 5.

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?

Two sentences, front-loaded with the core identity purpose, then a compact enumeration of the returned datasets. The list is long but each item carries information an agent cannot get elsewhere, since there is no output schema. Minor density cost from the stack of financial terms, but no 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?

No output schema exists, so the description has to carry the return-value burden, and it does so by enumerating the categories of data returned and noting the row counts per dataset. Combined with annotations covering safety and a fully documented single parameter, an agent has enough to call correctly. The remaining gap is error/empty-data behavior, which for a one-param read tool is a modest omission.

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?

There is a single parameter with 100% schema description coverage, and the schema already explains the ticker format including that 'BRK.B and BRK-B both work'. The description adds no further meaning about the ticker (no case sensitivity, no suffix rules, no behavior on invalid symbols). With the schema doing all the work, the baseline 3 applies.

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 names a specific verb-resource pair ('One company's identity') and enumerates the payload: name, exchange, industry, CIK, trailing twelve months, latest quarter and year, margins, cash flow, balance sheet, share count, plus per-dataset row counts. This is far more concrete than the title alone and lets an agent know it is a single-entity snapshot tool. It stops short of explicitly distinguishing itself from get_financials or search_companies, which is the only thing separating it from 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?

Usage is only implied: the required ticker parameter and the 'latest reported figures' framing suggest a one-company snapshot lookup. There is no statement of when to prefer this over get_financials (presumably historical series) or search_companies (ticker discovery), and no exclusions or prerequisites. An agent can infer the use case but must guess at the boundaries.

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