Skip to main content
Glama
Sign In
Polygon-io MCP Server

Polygon-io MCP Server

Official
by massive-com
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_benzinga_firms

Retrieve and filter Benzinga firms data using customizable parameters such as ID ranges, sorting, and limits on the Polygon-io MCP Server.

Instructions

List Benzinga firms.

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": "list_benzinga_firms"
  }
}

Input Schema

NameRequiredDescriptionDefault
benzinga_idNo
benzinga_id_any_ofNo
benzinga_id_gtNo
benzinga_id_gteNo
benzinga_id_ltNo
benzinga_id_lteNo
limitNo
paramsNo
sortNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.7/5.0
Behavior1/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 of behavioral disclosure. The description 'List Benzinga firms' reveals nothing about whether this is a read-only operation, whether it has side effects, what authentication might be required, rate limits, pagination behavior, error conditions, or response format. For a tool with 9 parameters and no annotation coverage, this is completely inadequate behavioral transparency.

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?

The description is maximally concise at just three words. While this represents severe under-specification rather than ideal conciseness, from a pure structural perspective, there is zero wasted language and the description is front-loaded with the core action. Every word earns its place, even though there are far too few words for adequate documentation.

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 complexity (9 parameters, no schema descriptions, no annotations, no output schema) and the fact this appears to be part of a financial data API with many similar listing tools, the description is completely inadequate. It provides no context about what 'Benzinga firms' are, how they differ from regular firms/tickers, what data is returned, how results are filtered/sorted, or how this tool relates to the many other list_* tools in the sibling set.

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?

The schema description coverage is 0%, meaning none of the 9 parameters have descriptions in the schema. The tool description provides absolutely no information about any parameters - not what they do, not which are required, not how they interact, not what 'Benzinga_id_gt' versus 'Benzinga_id_gte' means, not what the 'params' object should contain. With 9 undocumented parameters and no compensation in the description, this is a severe deficiency.

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 firms' is a tautology that essentially restates the tool name. It provides no additional specificity about what 'firms' means in this context or what distinguishes this listing operation from other list_* tools in the sibling set. While it does include the verb 'List' and resource 'Benzinga firms', it lacks any distinguishing details about scope, format, or purpose.

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?

The description provides absolutely no guidance about when to use this tool versus alternatives. With 9 sibling tools that also begin with 'list_' (like list_tickers, list_trades, list_quotes), there is no indication of what makes 'Benzinga firms' different or when this specific listing operation is appropriate. The description offers no context about prerequisites, typical use cases, or relationships to other tools.

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

Related Tools