Skip to main content
Glama
Sign In
Agent.ai MCP Server

Agent.ai MCP Server

by OnStartups
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

company_financial_info

Retrieve earnings reports for public companies by specifying stock symbol, quarter, and year.

Instructions

Gather company earnings information for public companies by quarter and year.

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": {
      "company": "<company>",
      "quarter": "<quarter>",
      "year": "<year>"
    },
    "name": "company_financial_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyYesStock symbol of the company.
quarterYesQuarter of the year to retrieve earnings info.
yearYesYear of the earnings info to retrieve.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only says 'gather' without detailing what is returned (e.g., revenue, EPS), whether the operation is read-only, or if there are rate limits or other constraints. This lack of behavioral context reduces transparency.

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 description is a single sentence, concise and front-loaded. It contains no redundant words. However, it could be slightly more informative without sacrificing brevity.

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

Completeness2/5

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

Given the lack of an output schema, the description should explain what kind of earnings information is returned (e.g., revenue, earnings per share). It does not, making it incomplete for an agent to fully understand the tool's output. The three parameters are well-covered by the schema, but the return value is opaque.

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?

The input schema has 100% coverage with clear descriptions for all three parameters (company, quarter, year). The description adds no new meaning beyond summarizing the timeframe ('by quarter and year'). Baseline 3 is appropriate as the schema does the heavy lifting.

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?

The description clearly states the tool gathers earnings information for public companies by quarter and year. It uses a specific verb ('gather') and resource ('earnings information'), and differentiates from siblings like 'company_financial_profile' which likely provides broader financial data. However, it doesn't explicitly distinguish itself from all siblings.

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 guidance on when to use this tool versus alternatives like 'company_financial_profile'. The description implies it is for earnings by quarter/year but does not state exclusions or prerequisites (e.g., requiring a public company ticker).

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

Deploy Server

Other Tools