Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

moneycontrol_sections

Lists all Moneycontrol news section slugs, names, and URLs accepted by the headlines tool, so you can pick valid sections like markets, economy, IPO, or cricket.

Instructions

Get Moneycontrol sections. Lists the 52 Moneycontrol news section slugs accepted by moneycontrol-headlines, such as markets, economy, ipo and cricket. Each entry has its slug, display name and page url. Moneycontrol Pro-only research, video, podcast and photo hubs are not sections.

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?

With no annotations, the description carries the behavioral burden. It discloses the return shape (slug, name, url), the 52-item scope, and which Moneycontrol hubs are excluded. It does not explicitly state read-only/no side effects, but 'Get'/'Lists' strongly implies a safe read operation.

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?

Four short sentences, front-loaded with purpose, then scope, examples, return fields, and an exclusion. Every sentence earns its place and there is no wasted text.

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?

For a simple zero-parameter list with no output schema, the description fully explains what is returned, how many items, what is excluded, and how the output relates to moneycontrol-headlines. Nothing needed 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 has zero parameters, so the baseline is 4. The description does not add parameter meaning because none exist, and it does not need to.

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 Moneycontrol sections' and 'Lists the 52 Moneycontrol news section slugs'. It gives example slugs and explicitly ties the output to moneycontrol-headlines, distinguishing it from article/news siblings.

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?

Explains that the slugs are accepted by moneycontrol-headlines, implying this tool should be used to discover valid section filters for that sibling. It also clarifies that Pro-only research, video, podcast, and photo hubs are excluded. It does not explicitly name alternative tools such as moneycontrol_news or state when not to use this tool.

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