Skip to main content
Glama
Sign In

APIVerve

by com.apiverve
OverviewDiscussionsAdmin

Income Statement

IncomeStatement
Read-only

Income Statement: Income Statement returns the profit and loss statement for a US public company by ticker - revenue, cost of revenue, gross profit, operating income and net income - straight from SEC filings, with gross, operating and net margins and year-over-year growth calculated for you. (Cost: 6 credits)

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": {
      "ticker": "<ticker>"
    },
    "name": "IncomeStatement"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoFiscal year to retrieve. Defaults to latest available. History covers only the quarters captured so far; a missing period answers 404 listing the available ones.
tickerYesStock ticker symbol (e.g. AAPL, MSFT, ADBE)
quarterNoFiscal quarter to retrieve. Defaults to latest available.

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNoError message, null on success
statusNo"ok" on success

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds real value beyond that: the data provenance (straight from SEC filings), the fact that margins and YoY growth are precomputed, and the 6-credit cost, which is operationally important for a metered tool.

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?

One dense but well-ordered sentence that front-loads the verb, resource, and scope, followed by the cost note in parentheses. Every clause carries information, though the run-on listing of fields and derived metrics could be trimmed slightly.

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 needn't describe return values, and it still usefully notes provenance, precomputed metrics, and credit cost for a read-only, open-world lookup. The only gap is the absence of any guidance on when to prefer this over sibling financial tools.

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% and the year/quarter parameters already document defaults and the 404-with-available-periods behavior, so the schema does the heavy lifting. The description adds no parameter-level detail beyond naming the ticker, 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 and resource ('returns the profit and loss statement'), narrows scope to 'US public company by ticker', and enumerates the returned line items plus derived margins, so an agent can tell it apart from BalanceSheet, CashFlowStatement, and EarningsReport without opening any schema.

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?

Usage is implied by the ticker input and the enumerated fields, but there is no explicit when-to-use or when-not guidance and no routing to close alternatives such as BalanceSheet, FinancialRatios, or EarningsReport for period-level detail.

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

All APIVerve 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