Equibles

Investor Relations News

GetInvestorRelationsNews

Read-only

Get recent investor-relations press releases for a stock, scraped from the company's IR website. Returns the most recent news items (headline, publish date, summary when the source provides one, and link) in reverse-chronological order. Use this to see a company's latest official announcements straight from its IR page, distinct from third-party news. Coverage is partial — only companies whose IR page has been discovered and content-scraped have items, so an empty answer may be a coverage gap rather than corporate silence; the response says which case applies.

Input Schema

Name	Required	Description
`since`	No	Optional earliest publish date, strict yyyy-MM-dd (UTC). Only items published on or after this date are returned.
`offset`	No	Number of matching news items to skip before returning rows (default: 0).
`ticker`	Yes	Company ticker symbol (e.g., NVDA), or MIC:TICKER (e.g., XPAR:AIR) for a listing outside the US.
`maxResults`	No	Maximum number of news items to return (default: 20, max: 500)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 15, 2026

changedInput schema / properties / ticker / description

Previous value: -"Company ticker symbol (e.g., NVDA)"New value: +"Company ticker symbol (e.g., NVDA), or MIC:TICKER (e.g., XPAR:AIR) for a listing outside the US."

Changed1 schema field changedSep 3, 2026

addedInput schema / properties / offset

Added value: +{
+  "default": 0,
+  "description": "Number of matching news items to skip before returning rows (default: 0).",
+  "type": "integer"
+}

First observedJul 19, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds genuinely useful behavior beyond that: partial coverage, the possibility of an empty result being a coverage gap rather than corporate silence, and that the response signals which case applies. It does not discuss pagination or rate/refresh behavior, keeping it short of a 5.

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?

Three sentences: purpose, return shape, and usage caveat. Front-loaded and mostly economical, though 'straight from its IR page, distinct from third-party news' slightly restates the opening source claim.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description usefully enumerates returned fields (headline, publish date, summary, link) and ordering (reverse-chronological). Combined with the coverage caveat, an agent has everything needed to call it and interpret an empty response.

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 100%, so since, offset, maxResults, and ticker are already fully documented with formats and defaults. The description adds no parameter-level detail (e.g., date syntax or pagination interaction), so the baseline 3 applies.

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?

The description gives a specific verb+resource ('Get recent investor-relations press releases for a stock') and adds the source scoping ('scraped from the company's IR website'), which cleanly separates it from third-party news tools in the sibling list. An agent can identify the tool's output and origin 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.

Usage Guidelines4/5

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

It states when to reach for this tool ('see a company's latest official announcements straight from its IR page, distinct from third-party news'), giving clear selection context. It stops short of naming a specific alternative sibling (e.g., a general news or web-data feed tool) or stating when-not-to-use, so it is not a full 5.

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

All Equibles tools Inspect

Try in Browser