Skip to main content
Glama

AIsa Equities

by one.aisa
OverviewDiscussionsAdmin

Get Earnings Data

get_financial_earnings
Read-onlyIdempotent

Get the most recent earnings snapshot for a ticker. Optional change fields are returned only when available.

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

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of most-recent **report periods** worth of filings to return, sorted by `(report_period DESC, filing_date ASC)`. The number of entries returned may exceed `limit` when a recent period has both an 8-K and a 10-Q / 10-K. Values above 40 are clamped to 40. Non-positive or non-integer values return 400. This is the total across all pages, not a page size: each page holds up to 10 records, linked by `next_page_url`.
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.
tickerYesThe ticker symbol (e.g. `AAPL`).

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
      Added value: +{
+  "default": 1,
+  "description": "Number of most-recent **report periods** worth of filings to return, sorted by `(report_period DESC, filing_date ASC)`. The number of entries returned may exceed `limit` when a recent period has both an 8-K and a 10-Q / 10-K. Values above 40 are clamped to 40. Non-positive or non-integer values return 400. This is the total across all pages, not a page size: each page holds up to 10 records, linked by `next_page_url`.",
+  "maximum": 40,
+  "minimum": 1,
+  "type": "integer"
+}
    • changedInput schema / properties / ticker / description
      Previous value: -"The ticker symbol."New value: +"The ticker symbol (e.g. `AAPL`)."
  2. Changed3 schema fields changed
    • removedInput schema / properties / cursor
      Removed 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"
-}
    • removedInput schema / properties / limit
      Removed value: -{
-  "default": 1,
-  "description": "Number of most-recent **report periods** worth of filings to return, sorted by `(report_period DESC, filing_date ASC)`. The number of entries returned may exceed `limit` when a recent period has both an 8-K and a 10-Q / 10-K. Values above 40 are clamped to 40. Non-positive or non-integer values return 400. This is the total across all pages, not a page size: each page holds up to 10 records, linked by `next_page_url`.",
-  "maximum": 40,
-  "minimum": 1,
-  "type": "integer"
-}
    • changedInput schema / properties / ticker / description
      Previous value: -"The ticker symbol (e.g. `AAPL`)."New value: +"The ticker symbol."
  3. 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
      Added value: +{
+  "default": 1,
+  "description": "Number of most-recent **report periods** worth of filings to return, sorted by `(report_period DESC, filing_date ASC)`. The number of entries returned may exceed `limit` when a recent period has both an 8-K and a 10-Q / 10-K. Values above 40 are clamped to 40. Non-positive or non-integer values return 400. This is the total across all pages, not a page size: each page holds up to 10 records, linked by `next_page_url`.",
+  "maximum": 40,
+  "minimum": 1,
+  "type": "integer"
+}
    • changedInput schema / properties / ticker / description
      Previous value: -"The ticker symbol."New value: +"The ticker symbol (e.g. `AAPL`)."
  4. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety and idempotency profile is covered without the description. The one extra bit — 'Optional change fields are returned only when available' — is a useful, non-obvious note about variable response shape, but that is the only behavioral 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?

The authored content is two tight, front-loaded sentences with no padding. The injected pricing block is boilerplate noise that dilutes the definition, but the substantive description itself is efficiently sized.

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

Completeness3/5

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

With a full output schema and complete annotations, the missing piece is routing guidance among many overlapping financial siblings. Return values need not be explained, so the only real gap is when to pick this over get_financial_financials or get_financial_analyst_estimates.

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 coverage is 100%, so the schema already fully documents ticker, limit, and cursor, including pagination and clamping behavior. The description adds nothing about parameters, which is acceptable at baseline when the schema carries the full load.

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?

States a specific verb and resource — 'Get the most recent earnings snapshot for a ticker' — so an agent knows it retrieves current earnings data keyed by ticker. However, it does not define what an 'earnings snapshot' contains or distinguish this tool from closely-named siblings like get_financial_financial_metrics_snapshot, get_financial_analyst_estimates, or get_financial_financials_income_statements.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No when-to-use guidance, no prerequisites, and no alternatives are named despite a crowded sibling set that overlaps heavily on financial fundamentals. The agent must infer selection from the name alone.

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