Skip to main content
Glama
tearsheet

tearsheet

by kewonit

screen_stocks

Read-only

Find listed companies matching financial and business conditions across the Indian market, with preset filters, sorting, and cursor-based paging for results.

Instructions

Find listed companies matching conditions, across the whole market.

    financial is a condition on exact field names, such as
    "Market Capitalization > 1000 AND ROCE > 20%". Find names with
    search_screen_fields. business filters on what companies do, such as
    "makes Steel" or "has plant in Gujarat". Or pass a preset name instead.
    Results are checked to make sure Tijori applied every filter. Use
    sort_by with a column name, and pass next_cursor back to page through
    results. Main board by default; set sme for SME listings.
    

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "screen_stocks"
  }
}

Input Schema

NameRequiredDescriptionDefault
smeNo
limitNo
cursorNo
presetNo
sort_byNo
businessNo
financialNo
descendingNo
latest_results_onlyNo
superstar_investorsNo

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

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, and the description adds real behavioral context beyond that: results are re-checked to confirm Tijori applied every filter, and paging is done by passing next_cursor back. It does not explain what latest_results_only or superstar_investors change about the result set, which are the least obvious behavioral switches.

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?

Compact and front-loaded, leading with purpose before filter-mode guidance and then pagination and board defaults. The embedded line breaks are only formatting artifacts and no sentence is redundant.

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 need no explanation, and the core screening workflow is well covered. However, four of ten parameters receive no description anywhere, including two non-obvious boolean toggles that an agent would have to guess at.

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 description coverage is 0%, so the description carries the full burden across 10 parameters. It explains financial, business, preset, sort_by, cursor, and sme with concrete example syntax, but leaves limit, descending, latest_results_only, and superstar_investors entirely unexplained.

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?

Opens with a specific verb and resource ('Find listed companies matching conditions, across the whole market'), which tells an agent exactly what the tool returns. It does not differentiate itself from lookup-style siblings like find_company or company_snapshot, 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 Guidelines4/5

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

Gives concrete usage guidance: use financial for field-based conditions, business for qualitative ones, or pass a preset name instead, and points to search_screen_fields to resolve field names. It also states the main-board default with sme as the override. It never says when to prefer a sibling tool over this one.

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