Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

benzinga_headlines

Fetch current story cards for one Benzinga editorial section—latest, technology-stocks, politics, or health-care—returning titles, URLs, summaries, authors, times, and images.

Instructions

Get Benzinga section headlines. Returns current Benzinga story cards for one section. section is required and is latest, technology-stocks, politics or health-care. Each item has a title and URL, and may also carry a summary, author, publication time and image.

Input Schema

NameRequiredDescriptionDefault
sectionYesBenzinga editorial section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose the return shape (title, URL, and optional summary/author/publication time/image), which is genuinely useful given there is no output schema. But it says nothing about authentication needs, rate limits, pagination, or result count, leaving meaningful gaps for a no-annotation 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?

Three sentences, front-loaded with the action and resource, then the required parameter, then the return contents. Efficient overall, though enumerating the enum values in prose mildly duplicates the schema.

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?

For a single-parameter read tool with no output schema, the description covers the required input and the fields returned, which is nearly everything an agent needs to call it. Only the safety/pagination profile is left implicit.

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 single param is an enum already fully documented in the schema. The description restates the four allowed values ('latest', 'technology-stocks', 'politics', 'health-care') but adds no semantics beyond the schema, so baseline 3 applies.

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 states a specific verb and resource ('Get Benzinga section headlines') and scopes it to one section. It doesn't explicitly distinguish itself from siblings like benzinga_news or benzinga_article, but the resource and cardinality (headlines for one section) are unambiguous.

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: 'for one section' with a required section slug tells the agent when the tool applies. However, there is no explicit guidance on when to prefer this over benzinga_news, benzinga_article, or benzinga_search, and no exclusions are stated.

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