Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

benzinga_article

Fetch a Benzinga editorial article by canonical URL, returning title, authors, dates, section, image, and body paragraphs.

Instructions

Get a Benzinga article. Returns a Benzinga article by url, a canonical dated editorial article URL: title, description, publication and update times, section, authors, image and the body paragraphs. Paid products, profiles, press releases, SEC pages and partner content are not accepted.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical dated Benzinga editorial article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4/5.0
Behavior4/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, and it does disclose the intake constraint (which URL classes are rejected) plus the composition of the returned payload (title, description, publication/update times, section, authors, image, body paragraphs). Gaps remain around failure behavior for invalid URLs and any auth or rate considerations, but the disclosure is well above the no-annotation baseline.

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 immediately followed by the return shape and the intake restriction. The opening two sentences partially restate each other ("Get a Benzinga article. Returns a Benzinga article by `url`"), a minor redundancy that keeps it from a 5.

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?

There is no output schema, so the description must describe returns, and it does so field-by-field for a single-parameter read tool. Combined with the accepted-URL constraint, an agent has enough to call this correctly; only error/edge-case behavior is unaddressed.

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

Parameters4/5

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

Schema coverage is 100% and the schema already defines `url` as a canonical dated Benzinga editorial article URL, so the baseline is 3. The description adds genuine semantic value by enumerating the URL classes that are rejected, which is not encoded anywhere in the schema.

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 a Benzinga article ... by `url`") and scopes it to "canonical dated editorial article" content, which meaningfully distinguishes it from sibling list/feed tools like benzinga_headlines, benzinga_news, and benzinga_search. It stops short of naming any sibling explicitly, so it lands at 4 rather than 5.

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

Usage Guidelines4/5

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

It gives actionable negative guidance — paid products, profiles, press releases, SEC pages, and partner content are not accepted — which tells the agent when this tool is the wrong choice. It does not, however, state where a valid `url` should come from or point to the headline/search siblings for discovery, so the positive usage context is only implied.

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