Skip to main content
Glama
screener-mcp
by LogeshR15

get_quarterly_results

Read-only

Retrieve a company's last eight quarters of financial results—revenue, expenses, operating profit, OPM, net profit, and EPS—to analyze quarter-on-quarter growth and seasonality.

Instructions

Get the last 8 quarters of results for a company.

Shows: Revenue, Expenses, Operating Profit, OPM%, Net Profit, EPS Useful for identifying quarter-on-quarter growth trends and seasonality.

symbol: NSE/BSE symbol (e.g., "TCS", "WIPRO", "MARUTI")

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

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

B3.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the metric coverage, which helps the agent judge whether the result is sufficient, but says nothing about the consolidated vs standalone basis, currency, or data-lag behavior. With annotations carrying the safety layer, this is adequate but thin.

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?

It is front-loaded with the core action, then the metric list, then the parameter hint; each block is useful and there is no padding. The trailing `symbol:` line is slightly orphaned in structure but adds real value.

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?

An output schema exists, so return values do not need explanation and the metric list is a bonus. However, for a two-parameter financial-data tool, leaving the consolidated/standalone switch entirely unexplained and giving no hint of currency, coverage universe, or failure behavior for an invalid symbol leaves a meaningful gap.

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 coverage is 0%, so the description must carry the parameter burden itself. It does explain `symbol` with concrete NSE/BSE examples (TCS, WIPRO, MARUTI), but it never mentions `financial_type`, which defaults to consolidated and materially changes the numbers returned, and is the more subtle of the two. Half the parameters are undocumented.

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 resource plus an explicit scope: 'Get the last 8 quarters of results for a company.' That the window is exactly 8 quarters and the metric list is enumerated sets it apart from a generic financials tool. It does not name or contrast itself with the sibling get_financials, keeping it out of 5 territory.

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?

'Useful for identifying quarter-on-quarter growth trends and seasonality' implies the analytical context in which the tool is appropriate, but there is no explicit when-not guidance and no sibling is named as an alternative, even though get_financials exists. 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.