Skip to main content
Glama
massive-com

Polygon-io MCP Server

Official

list_benzinga_ratings

Retrieve Benzinga ratings for stocks by filtering specific criteria such as date, ticker, rating action, and importance. Use this tool to analyze analyst insights and track price target actions efficiently.

Instructions

List Benzinga ratings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
benzinga_analyst_idNo
benzinga_analyst_id_any_ofNo
benzinga_analyst_id_gtNo
benzinga_analyst_id_gteNo
benzinga_analyst_id_ltNo
benzinga_analyst_id_lteNo
benzinga_firm_idNo
benzinga_firm_id_any_ofNo
benzinga_firm_id_gtNo
benzinga_firm_id_gteNo
benzinga_firm_id_ltNo
benzinga_firm_id_lteNo
benzinga_idNo
benzinga_id_any_ofNo
benzinga_id_gtNo
benzinga_id_gteNo
benzinga_id_ltNo
benzinga_id_lteNo
dateNo
date_any_ofNo
date_gtNo
date_gteNo
date_ltNo
date_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
price_target_actionNo
price_target_action_any_ofNo
price_target_action_gtNo
price_target_action_gteNo
price_target_action_ltNo
price_target_action_lteNo
rating_actionNo
rating_action_any_ofNo
rating_action_gtNo
rating_action_gteNo
rating_action_ltNo
rating_action_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 fails to mention any aspects like read-only vs. destructive operations, authentication needs, rate limits, pagination, or response format. The single sentence offers no behavioral context beyond the basic action, leaving critical operational details unspecified.

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?

While concise with a single sentence, the description is under-specified rather than efficiently informative. It lacks front-loaded critical details and fails to provide necessary context, making it ineffective despite its brevity. Every sentence should earn its place, but this one adds minimal value beyond the tool name.

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 does not compensate for the lack of structured data, leaving the tool's functionality, behavior, and usage opaque. A list operation with many filtering options requires much more explanation to be usable.

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 information about parameters, such as their purposes, relationships (e.g., filtering by analyst ID or date ranges), or usage examples. This leaves all parameters semantically undocumented, severely hindering effective tool invocation.

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 ratings' restates the tool name with minimal elaboration, making it a tautology. It lacks specificity about what 'ratings' entail (e.g., financial analyst ratings, stock ratings) and does not differentiate from sibling tools like 'list_benzinga_consensus_ratings', leaving the purpose vague and under-defined.

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?

No guidance is provided on when to use this tool versus alternatives, such as sibling tools like 'list_benzinga_consensus_ratings' or other data retrieval tools. The description offers no context, prerequisites, or exclusions, making it impossible for an agent to determine appropriate usage scenarios.

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