Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

benzinga_sections

List all Benzinga editorial news sections to find valid slugs for headline queries. Returns names, slugs, and page URLs for latest, technology-stocks, politics, and health-care.

Instructions

List Benzinga news sections. Lists the four Benzinga editorial sections accepted by benzinga-headlines: latest (named Breaking News), technology-stocks, politics and health-care. Each has a slug, a display name and the section's page url.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4.5/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 return shape (each section has a slug, display name and page url) plus the exact values returned. The only gap is that it never explicitly labels the operation as a read-only, side-effect-free lookup, which for a zero-parameter lister is a minor omission.

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?

Two sentences, front-loaded with the verb and resource, then the enumerated values. Nothing is redundant and every clause (slugs, names, urls) adds information an agent would otherwise have to discover by calling the tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description compensates by naming the three returned fields (slug, name, url) and listing all enum values, and with zero parameters and a simple read-only surface nothing an agent needs in order to call it correctly is missing.

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?

The tool takes no parameters, so per the rubric the baseline is 4. The description appropriately spends no words on argument syntax and instead uses the space to describe the returned fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (List) and resource (Benzinga news sections) and enumerates the exact four sections returned, which cleanly distinguishes it from benzinga_headlines, benzinga_article and benzinga_news. An agent knows immediately this is a taxonomy/enumeration lookup, not a content-fetching tool.

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?

The description ties the tool to `benzinga-headlines` by stating these are the sections that tool accepts, which implicitly tells the agent to call this first to discover valid section values. It stops short of an explicit 'call this before benzinga_headlines' directive or any exclusion criteria, so it is clear context without full routing instructions.

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