Skip to main content
Glama

News releases from a company

get_company_news_releases
Read-onlyIdempotent

Use this when someone asks what a listed company announced, or wants its latest or past news releases. Give it the company's ticker (AAPL, NYSE:BAC) or name. Returns its releases newest first, each with date, headline and 6ix.com link; read one in full with get_news_release. Every release 6ix holds for the company can be reached: pass the answer's nextCursor as cursor to go further back.

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": {
      "company": "<company>"
    },
    "name": "get_company_news_releases"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage 2 and on go further back in time
limitNo
cursorNoTo read on: nextCursor from this tool's last answer, exactly as given, with the same other arguments
companyYesTicker (AAPL, NYSE:BAC, SHOP.TO), company name, or the 6ix company link returned by find_company

Output Schema

NameRequiredDescriptionDefault
asOfNoWhen 6ix answered (ISO 8601, UTC)
pageYesThe page read; null when read on from a cursor
companyYes
hasMoreYesMore follow: ask again with cursor set to nextCursor
releasesYes
nextCursorYesPass as cursor to read on from the last item shown; null at the end
listChangedNoThe list changed since the cursor was made and the last item shown is no longer in it, so an item may repeat or be missed here

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • addedInput schema / properties / cursor
      Added value: +{
      +  "description": "To read on: nextCursor from this tool's last answer, exactly as given, with the same other arguments",
      +  "maxLength": 700,
      +  "minLength": 8,
      +  "type": "string"
      +}
    • changedInput schema / properties / page / maximum
      Previous value: -50New value: +10000
    • addedOutput schema / properties / hasMore / description
      Added value: +"More follow: ask again with cursor set to nextCursor"
    • addedOutput schema / properties / listChanged
      Added value: +{
      +  "description": "The list changed since the cursor was made and the last item shown is no longer in it, so an item may repeat or be missed here",
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / nextCursor
      Added value: +{
      +  "description": "Pass as cursor to read on from the last item shown; null at the end",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / page / description
      Added value: +"The page read; null when read on from a cursor"
    • changedOutput schema / properties / page / type
      Previous value: -"integer"New value: +[
      +  "integer",
      +  "null"
      +]
    • changedOutput schema / required
      Previous value: -[
      -  "company",
      -  "releases",
      -  "page",
      -  "hasMore"
      -]New value: +[
      +  "company",
      +  "releases",
      +  "page",
      +  "hasMore",
      +  "nextCursor"
      +]
  2. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds real behavioral context beyond that: results are ordered newest first, each carries date/headline/link, and pagination continues via nextCursor->cursor to reach 'every release 6ix holds.'

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, all front-loaded and load-bearing: trigger, input format, output shape, sibling routing, and pagination. No filler or repetition of names.

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?

With an output schema present, the description need not detail return values, yet it still summarizes them usefully and covers pagination continuity. It is nearly complete; only the absence of guidance against near-duplicate siblings leaves a small gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 75% schema coverage the baseline is already high, but the description adds value: it shows accepted company formats (AAPL, NYSE:BAC) and explains the cursor round-trip ('pass the answer's nextCursor as cursor ... with the same other arguments'), which supplements the schema's cursor note. It does not clarify 'limit' or the page-vs-cursor relationship.

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?

The description states a specific verb+resource ('what a listed company announced ... its latest or past news releases') and clarifies scope by noting releases are returned newest first with a 6ix.com link. It distinguishes itself from get_news_release ('read one in full with get_news_release'), but does not differentiate from siblings like get_latest_news_releases or search_news_releases, which an agent could easily confuse it with.

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 gives clear usage context ('Use this when someone asks what a listed company announced, or wants its latest or past news releases') and routes to the sibling for full-text reading. However, it offers no explicit when-not guidance versus get_latest_news_releases or search_news_releases, leaving the agent to infer the boundary.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources