Skip to main content
Glama
screener-mcp
by LogeshR15

search_market_commentary

Read-only

Search multiple companies' indexed documents at once to answer one question, such as which firms cited raw material cost pressure. Finds relevant commentary across symbols without downloading new documents.

Instructions

Semantic search for a question across MULTIPLE companies' already-indexed documents at once — e.g. "which of these companies mentioned raw material cost pressure in their recent earnings calls?"

Only searches documents already indexed via ask_company_research for each symbol — it does NOT download new documents, so cost/latency stays bounded no matter how many symbols are passed. Run ask_company_research(symbol, ...) first for any symbol you want included that hasn't been indexed yet.

Requires: pip install pdfplumber sentence-transformers chromadb

Examples: search_market_commentary("raw material cost pressure", ["TATASTEEL", "JSWSTEEL", "SAIL"]) search_market_commentary("management outlook on margins", ["ITC", "HINDUNILVR", "NESTLEIND"])

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": {
      "question": "<question>",
      "symbols": "<symbols>"
    },
    "name": "search_market_commentary"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolsYes
questionYes
top_k_per_symbolNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds genuinely new behavior: results are limited to the pre-built index, so cost and latency stay bounded regardless of symbol count, and third-party packages are required. It stops short of describing ranking or result-shape behavior, which is partly covered by the 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-loads the core capability and scope, then the prerequisite, then the requirement and examples. The dependency-install line is mildly operational noise but still actionable; the two example calls are well spent for illustrating argument shape.

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?

Covers the workflow dependency, the bounded-cost guarantee, and query semantics for a tool whose return values are documented by an existing output schema. The only real hole is the undocumented `top_k_per_symbol` knob, which affects how many hits come back per company.

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 effectively illustrates `question` (natural-language query with two examples) and `symbols` (list of tickers in the example calls), but `top_k_per_symbol` is never mentioned, leaving one of three parameters undocumented anywhere.

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?

States a specific verb and resource — semantic search over already-indexed documents — and explicitly scopes it to MULTIPLE companies at once, which cleanly separates it from ask_company_research's per-symbol behavior. The inline example question makes the retrieval model concrete.

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

Usage Guidelines5/5

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

Gives an explicit prerequisite (run ask_company_research(symbol, ...) first for any unindexed symbol) and an explicit non-capability (it does NOT download new documents). An agent knows both when this tool is appropriate and what must happen before calling it.

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