Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

businessstandard_sections

List the 25 Business Standard section slugs accepted by businessstandard-headlines, from latest-news and companies to cricket and todays-paper, each with its name and page URL.

Instructions

Get Business Standard sections. Lists the 25 Business Standard section slugs accepted by businessstandard-headlines, from latest-news, companies and markets to cricket, immigration and todays-paper. Each entry 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.5

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 disclosure burden. It does so reasonably well for a side-effect-free lookup: it reveals the result size (25 entries), the fact that other tools consume these slugs, and the shape of each entry (`slug`, `name`, `url`). It does not discuss caching or whether the list is stable, but for a zero-parameter read that is a minor gap.

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 sentences, front-loaded with the purpose, then the scope and the concrete slug examples, then the entry shape. Nothing is redundant and every sentence adds a distinct fact.

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?

There is no output schema, yet the description fully specifies the return fields (`slug`, `name`, `url`) and the entry count, so an agent knows exactly what it will receive. Combined with the explicit link to `businessstandard-headlines`, nothing needed to call this 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 zero parameters, so the baseline is 4. The description appropriately spends no words on inputs and instead documents what the entries contain, which is the semantically useful information here.

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 and resource ('Get Business Standard sections') and immediately characterizes the payload as the 25 section slugs accepted by `businessstandard-headlines`, listing representative values. An agent can distinguish this lookup tool from `businessstandard_article`, `businessstandard_news` and `businessstandard_headlines` without opening any schema.

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 makes the usage condition clear by naming `businessstandard-headlines` as the consumer of these slugs, which tells an agent to call this first when it needs a valid section value. It stops short of an explicit 'use this instead of X when Y' statement, but the routing intent is unambiguous.

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