Skip to main content
Glama

FinanceQuery

Company Press Releases

get_press_releases
Read-onlyIdempotent

Get a company's own press releases, distinct from get_news (press coverage). Routes through EDGAR 8-K exhibits, falling back to FMP/Alpha Vantage when configured.

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": {
      "symbol": "<symbol>"
    },
    "name": "get_press_releases"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of releases to return (default: 10)
fieldsNoComma-separated list of GraphQL field names to include; omitted = all fields
symbolYesStock ticker symbol

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description is free to add the more valuable detail: results are sourced primarily from EDGAR 8-K exhibits with FMP/Alpha Vantage as fallback only when configured. That tells the agent output coverage and reliability can vary by deployment, which is real behavioral context beyond the annotations. It stops short of describing ordering, latency, or empty-result behavior.

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?

Two tight sentences with no filler; the scope and sibling distinction come first and the source-routing detail follows. Every clause carries information an agent would actually use.

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?

For a three-parameter read-only tool with full schema coverage and no output schema, the description supplies the two things the structured fields cannot: differentiation from get_news and the underlying data-source fallback. Nothing essential to correct invocation is missing, though a note on result ordering or behavior when no releases exist would round it out.

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% — symbol, limit with default, and fields are all documented in the schema — so the baseline applies. The description adds no extra meaning about the parameters, such as how limit interacts with fallback sources or what the fields string accepts.

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 ("Get a company's own press releases") and immediately distinguishes the scope from the sibling get_news by labeling that one as press coverage. An agent can tell the two apart without opening either 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?

Explicitly names the alternative (get_news) and the condition that selects it (company's own releases vs. third-party coverage). It does not address when to prefer other filing-oriented siblings such as get_edgar_search or get_filing_sections, so the routing guidance is clear but not exhaustive.

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.