Skip to main content
Glama
Screener India MCP

Screener India MCP

price_history

Read-onlyIdempotent

Retrieve daily historical Indian stock metrics—including price with 50/200-day averages and volume, PE, margins, EV/EBITDA, PB, and market cap/sales—over a chosen lookback period.

Instructions

Daily history. metric: price (with 50/200-day averages and volume) | pe | margins | ev_ebitda | pb | mcap_sales. days snaps to 30, 90, 180, 365, 1095, 1825, 3652 or 10000.

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

Input Schema

NameRequiredDescriptionDefault
daysNo
metricNoprice
symbolYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare the tool is read-only, idempotent, open-world, and non-destructive. The description adds useful behavioral context by stating that days snaps to specific values and that price includes 50/200-day averages and volume, but it omits other relevant traits such as data adjustment or return shape.

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 description is two compact sentences with no filler and is front-loaded with the metric enumeration. The pipe-separated formatting is dense, but it remains efficient and appropriately sized for the information provided.

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?

For a three-parameter retrieval tool with no output schema, the description gives enough to invoke the tool with a metric and snapped day range, but it does not explain the symbol format or the exact returned data structure. It is minimally viable but has clear completeness gaps.

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 0%, so the description must carry parameter meaning. It partially compensates by listing allowed metric values and the days snapping behavior, but it does not describe the required symbol parameter or clarify defaults, leaving a clear gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says "Daily history" and enumerates metric choices, so the agent can infer it returns historical daily data for a symbol. However, it lacks an explicit verb and resource statement such as "retrieves daily price/metric history for a company," leaving the core purpose somewhat vague.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description lists metric options and day-range snapping, but never says when to use this tool versus siblings like company_snapshot, financial_statement, or company_overview. There are no explicit inclusion or exclusion conditions for tool selection.

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