Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

benzinga_search

Search news-article suggestions and return up to five public matches from a finance news typeahead; ticker-only results are omitted, and it is not a paginated archive search.

Instructions

Search Benzinga article suggestions. Returns up to five public news-article suggestions from Benzinga's anonymous search typeahead. Ticker-only suggestions are omitted; this is not a paginated archive search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesSearch text (2 to 100 characters)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does meaningful work: it discloses the result cap (up to five), the anonymous typeahead source, the omission of ticker-only suggestions, and the non-paginated nature. It stops short of stating auth/permission requirements or rate-limit behavior, so it is strong but not exhaustive.

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?

Three tight sentences with the core purpose front-loaded, then result count and exclusions. No padding or repetition; every sentence carries information the agent needs.

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 one-parameter typeahead with no output schema and no annotations, the description covers the essentials an agent needs (source, result cap, exclusions, non-paginated scope). Minor gaps remain around what an empty or no-match query returns and any auth expectations, but nothing critical is missing.

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 coverage is 100% and the single 'q' parameter is already documented as 2-100 character search text, so the baseline is 3. The description adds no syntax, operator, or query-shaping guidance beyond what the schema supplies.

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?

States a specific verb (Search) and resource (Benzinga article suggestions), and clarifies the mechanism as an anonymous typeahead rather than a full archive. It does not name the sibling tools (benzinga_article, benzinga_headlines, benzinga_news) it competes with, so sibling differentiation is implicit rather than explicit.

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?

The line 'this is not a paginated archive search' gives a negative usage signal, steering the agent away for archive-style lookups, but it never names the alternative tools or states the positive condition under which this typeahead should be chosen over benzinga_article/benzinga_headlines.

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