India and US news stories linked to listed companies, commodities and indices, with sources.
Scored across 1 tool
Only one tool is provided, so there is no risk of tool confusion or overlapping purposes. The single tool has a clear, distinct scope.
The single tool follows a clear snake_case verb_noun convention (search_stories), and there are no other names to compare against for consistency.
With only one tool, the server feels thin even for a narrow news-search purpose. Additional operations like fetching story details or listing sources could reasonably be expected, so 1 tool is borderline.
The tool covers search with paging and optional query, but lacks operations to retrieve a specific story by ID, list available sources, or filter by instrument type or date range beyond 48 hours. These are notable gaps for a news retrieval surface.
News stories from the last 48 hours for one country (IN or US) that are linked to a listed company, commodity, index or the rupee. Each story says what it reports about those instruments and names up to three sources. Information only — never investment advice. Without a query it returns the most relevant stories; with one, the stories that mention the query's words. Results are paged with a cursor.
| Name | Required | Description | Default |
|---|---|---|---|
| hours | No | Lookback window in hours, default 24, max 48 — older stories are purged. | |
| limit | No | Stories per page, default 5, max 10. | |
| query | No | Words to look for, e.g. a company, commodity or topic: 'crude oil', 'Reliance', 'RBI'. | |
| cursor | No | next_cursor from the previous page of the same search. Omit for the first page. | |
| country | Yes | Market the story affects: 'IN' (India) or 'US'. |
| Name | Required | Description |
|---|---|---|
| code | Yes | |
| total | Yes | |
| country | Yes | |
| stories | Yes | |
| next_cursor | Yes | |
| window_hours | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover readOnly/idempotent/non-destructive. The description adds useful context beyond them: 'Information only — never investment advice' frames the content, source count (up to three) and cursor paging disclose return shape, and the 48-hour purge window is implied. No rate limits or auth notes, but solid added value.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Front-loaded with what the tool returns, then behavior, then paging. Every sentence carries distinct information; no padding or repetition of the title.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
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 not be explained. Given moderate complexity and full schema coverage, the description supplies everything an agent needs: scope, query behavior, and paging.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so every parameter is already documented, giving a baseline of 3. The description adds query semantics (with/without) and the 48-hour window tied to the hours param, but no syntax beyond what the schema already provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (search/list) and resource (news stories) with clear scope: last 48 hours, one country, linked to a listed company/commodity/index/rupee. An agent knows exactly what it gets without opening the schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Clearly explains the query-on/query-off behavior ('Without a query it returns the most relevant stories; with one, the stories that mention the query's words'), which tells the agent when the query param matters. No siblings exist, so there are no alternatives to route between, but there are no explicit exclusions either.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
search_storiesIndian stocks: NSE/BSE filings read by AI with price reactions, fundamentals, IPOs and FPI flows.
Structured company & industry news for AI agents: typed, dated, source-linked events.
SEBI orders, RBI notifications, MCA filings, NSE/BSE announcements, AMFI NAV.
US market snapshot, stock fundamentals, prices, statements, news and analyst views
Add one secure layer between your agents and this server.