API Ninjas

getIncomeStatementAvailability

Read-only

Returns the fiscal years and quarters for which income statement data is available for a company. Requires a premium subscription (Developer tier and above).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "getIncomeStatementAvailability"
  }
}

Input Schema

Name	Required	Description	Default
`cik`	No	Company Central Index Key (e.g., 796343). Either ticker or cik must be provided.
`ticker`	No	Company ticker symbol (e.g., ADBE). Either ticker or cik must be provided.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 9, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already confirm readOnlyHint=true, so the safety profile is covered. The description adds genuinely non-obvious context beyond annotations: the tool requires a premium subscription at Developer tier or above. No pagination or response-shape detail, but for a lightweight availability probe that gap is minor.

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: the primary behavior is front-loaded, and the subscription caveat follows immediately. There is no filler.

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?

For a simple two-parameter read tool with full schema coverage, the description supplies what matters: what is returned (fiscal years and quarters) and the access prerequisite. Nothing an agent needs to call it correctly is missing.

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 both cik and ticker are fully documented in the schema, including the 'either must be provided' constraint. The description adds no parameter-level detail beyond that, 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?

States a specific verb (Returns) and resource (the fiscal years and quarters for which income statement data is available for a company). It clearly distinguishes itself from the sibling getIncomeStatement, which returns the data itself rather than coverage metadata.

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

Usage Guidelines3/5

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

It surfaces a prerequisite (premium subscription, Developer tier and above), which is useful. However, it never explicitly states when to prefer this tool over getIncomeStatement or the other availability siblings (balance sheet, cash flow), leaving the relationship to inference.

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

All API Ninjas tools Inspect

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

Need Help?