Skip to main content
Glama
massive-com

Polygon-io MCP Server

Official

list_benzinga_earnings

Fetch and filter Benzinga earnings data by date, ticker, importance, fiscal details, and surprise percentages for detailed financial analysis.

Instructions

List Benzinga earnings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNo
date_any_ofNo
date_gtNo
date_gteNo
date_ltNo
date_lteNo
date_statusNo
date_status_any_ofNo
date_status_gtNo
date_status_gteNo
date_status_ltNo
date_status_lteNo
eps_surprise_percentNo
eps_surprise_percent_any_ofNo
eps_surprise_percent_gtNo
eps_surprise_percent_gteNo
eps_surprise_percent_ltNo
eps_surprise_percent_lteNo
fiscal_periodNo
fiscal_period_any_ofNo
fiscal_period_gtNo
fiscal_period_gteNo
fiscal_period_ltNo
fiscal_period_lteNo
fiscal_yearNo
fiscal_year_any_ofNo
fiscal_year_gtNo
fiscal_year_gteNo
fiscal_year_ltNo
fiscal_year_lteNo
importanceNo
importance_any_ofNo
importance_gtNo
importance_gteNo
importance_ltNo
importance_lteNo
last_updatedNo
last_updated_any_ofNo
last_updated_gtNo
last_updated_gteNo
last_updated_ltNo
last_updated_lteNo
limitNo
paramsNo
revenue_surprise_percentNo
revenue_surprise_percent_any_ofNo
revenue_surprise_percent_gtNo
revenue_surprise_percent_gteNo
revenue_surprise_percent_ltNo
revenue_surprise_percent_lteNo
sortNo
tickerNo
ticker_any_ofNo
ticker_gtNo
ticker_gteNo
ticker_ltNo
ticker_lteNo
Behavior1/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It offers no information on safety (e.g., read-only vs. destructive), permissions, rate limits, pagination, or output format. The description is too minimal to convey any behavioral context, leaving the agent uninformed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, under-specified sentence that lacks necessary detail, making it inefficient rather than concise. It does not front-load key information and wastes the opportunity to provide value, as it is too brief for the tool's complexity.

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

Completeness1/5

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

Given the high complexity (57 parameters), no annotations, no output schema, and 0% schema coverage, the description is completely inadequate. It fails to address purpose, usage, behavior, or parameters, leaving the agent unable to effectively select or invoke the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 57 parameters and 0% schema description coverage, the schema provides only titles without explanations. The description adds no parameter semantics, failing to explain what parameters like 'date_gt', 'eps_surprise_percent', or 'limit' do or how they filter earnings data, leaving all parameters undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'List Benzinga earnings' restates the tool name with minimal elaboration, making it a tautology. It lacks specificity about what 'earnings' entails (e.g., earnings reports, data, announcements) and does not differentiate from sibling tools like 'list_benzinga_news' or 'list_stock_financials', leaving the purpose vague.

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool versus alternatives. The description does not mention context, prerequisites, or exclusions, and it fails to reference any sibling tools (e.g., 'list_benzinga_news' for news or 'list_stock_financials' for financial data), providing no usage direction.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/massive-com/mcp_massive'

If you have feedback or need assistance with the MCP directory API, please join our Discord server