Skip to main content
Glama

AIsa Equities

by one.aisa
OverviewDiscussionsAdmin

Get Company News

get_financial_news
Read-onlyIdempotent

Get recent news articles for a specific company or the broad market. Pass a ticker for company-specific news, or omit the ticker for general market news.

Published reference price: $0.02 USD per successful request. Account-specific pricing and final settlement may differ.

Input Schema

NameRequiredDescriptionDefault
limitNoThe maximum number of news articles to return (default: 5, max: 10). This is the total across all pages, not a page size: each page holds up to 10 records, linked by `next_page_url`. Provider reference (supplier schema): `{"default":5,"maximum":10,"type":"integer"}`.
cursorNoOpaque pagination cursor from a previous response's next_page_url. When provided, all other query parameters are ignored: the cursor carries the original request's filters. Treat it as opaque; do not construct or modify it.
tickerNoThe ticker symbol of the company. Omit for broad market news.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / cursor
      Added value: +{
+  "description": "Opaque pagination cursor from a previous response's next_page_url. When provided, all other query parameters are ignored: the cursor carries the original request's filters. Treat it as opaque; do not construct or modify it.",
+  "type": "string"
+}
    • addedInput schema / properties / limit / description
      Added value: +"The maximum number of news articles to return (default: 5, max: 10). This is the total across all pages, not a page size: each page holds up to 10 records, linked by `next_page_url`.\n\nProvider reference (supplier schema): `{\"default\":5,\"maximum\":10,\"type\":\"integer\"}`."
    • addedInput schema / properties / ticker / description
      Added value: +"The ticker symbol of the company. Omit for broad market news."
  2. Changed5 schema fields changed
    • removedInput schema / properties / limit / default
      Removed value: -5
    • removedInput schema / properties / limit / description
      Removed value: -"The maximum number of news articles to return (default: 5, max: 10)."
    • removedInput schema / properties / limit / maximum
      Removed value: -10
    • changedInput schema / properties / limit / type
      Previous value: -"integer"New value: +"string"
    • removedInput schema / properties / ticker / description
      Removed value: -"The ticker symbol of the company. Omit for broad market news."
  3. Changed5 schema fields changed
    • addedInput schema / properties / limit / default
      Added value: +5
    • addedInput schema / properties / limit / description
      Added value: +"The maximum number of news articles to return (default: 5, max: 10)."
    • addedInput schema / properties / limit / maximum
      Added value: +10
    • changedInput schema / properties / limit / type
      Previous value: -"string"New value: +"integer"
    • addedInput schema / properties / ticker / description
      Added value: +"The ticker symbol of the company. Omit for broad market news."
  4. Changed5 schema fields changed
    • removedInput schema / properties / limit / default
      Removed value: -5
    • removedInput schema / properties / limit / description
      Removed value: -"The maximum number of news articles to return (default: 5, max: 10)."
    • removedInput schema / properties / limit / maximum
      Removed value: -10
    • changedInput schema / properties / limit / type
      Previous value: -"integer"New value: +"string"
    • removedInput schema / properties / ticker / description
      Removed value: -"The ticker symbol of the company. Omit for broad market news."
  5. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare the full safe-read profile (readOnly, idempotent, non-destructive, openWorld), so the safety bar is low. The description adds the dual-mode behavior, but says nothing about freshness/coverage window, rate limits, or result ordering; the pricing line is injected boilerplate rather than authored disclosure.

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?

Two short sentences, capability first and operational detail second, with zero filler in the authored text. The second sentence partially restates the dual-mode idea from the first, a minor redundancy; the trailing pricing block is auto-injected and not the author's conciseness burden.

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?

An output schema exists and the input schema fully documents all three parameters including pagination semantics, so the description need not explain returns. It still omits any hint about how far back news goes or how results are ordered, a small gap for a news tool but not one that blocks correct invocation.

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 the schema already carries the meaning of limit, cursor, and ticker (including "Omit for broad market news"), making 3 the correct baseline. The description's ticker guidance duplicates rather than extends the schema, adding no new syntax or constraint detail.

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 recent news articles") and immediately clarifies the two operating modes: ticker-specific news vs. broad market news. No sibling among the get_financial_* tools overlaps with news retrieval, so the agent can route to it unambiguously from the name and first sentence.

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 tells the agent how to select between the two modes ("Pass a ticker for company-specific news, or omit the ticker for general market news"), which is the main decision point. It stops short of naming alternatives for adjacent questions (e.g., filings or earnings coverage), so no exclusions are given.

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

All AIsa Equities toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources