Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

businessstandard_headlines

Retrieve Business Standard section headlines by section slug, returning up to 35 stories or 100 for latest-news. Use it to monitor news sections such as companies, markets, or cricket.

Instructions

Get Business Standard section headlines. Returns recent headlines for one Business Standard section: up to 35 stories, or 100 for latest-news. section is required and takes one of 25 slugs such as companies, markets, cricket or todays-paper. Some stories are premium (subscriber-only), and requesting one from the article endpoint returns 403.

Input Schema

NameRequiredDescriptionDefault
sectionYesBusiness Standard section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

B3.2/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It adds genuine behavioral detail beyond the schema: result caps (35 stories, or 100 for latest-news) and the premium/subscriber-only caveat with the 403 from the article endpoint. It still omits freshness, pagination, and whether premium items are filtered out of results entirely.

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 front-loaded sentences with no filler: purpose first, then the result-count behavior, then the premium caveat. Tight and easy to scan.

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 listing tool with no output schema or annotations, it covers the essentials: what is returned, the count limits, and the premium access caveat. Missing only minor items like freshness window and pagination.

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% with a fully enumerated 25-value slug list, so the baseline is 3. The description restates the slug examples and notes that 'latest-news' behaves differently (100 vs 35), which adds marginal value over the enum but little beyond it.

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 and resource ('Get Business Standard section headlines') and specifies scope ('one Business Standard section'). It does not, however, differentiate itself from close siblings like businessstandard_news or businessstandard_sections, so the agent must infer which one to pick.

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

Usage Guidelines2/5

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

No explicit when-to-use or when-not-to-use guidance. It never says how this differs from businessstandard_news, businessstandard_sections, or businessstandard_article, leaving the routing decision entirely to inference despite many near-identical siblings.

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