Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

moneycontrol_headlines

Fetch current Moneycontrol headlines for a chosen section slug, returning 25 or 50 stories with title, URL, summary, and image URL for quick topic monitoring.

Instructions

Get Moneycontrol section headlines. Returns the current front page of one Moneycontrol section: 25 or 50 stories, each with title, url, a short summary and image_url. section is required and takes one of 52 slugs such as markets, ipo or cricket; other values return 400. Publication time and author are omitted, and only the first page is available.

Input Schema

NameRequiredDescriptionDefault
sectionYesMoneycontrol section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.2/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and does so well: it discloses the return cardinality (25 or 50 stories), the exact fields returned, that invalid slugs return 400, and the notable limitations (no publication time, no author, first page only). These are meaningful operational facts an agent cannot infer elsewhere.

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 front-loaded sentences, no filler. Purpose comes first, then return shape, then the parameter constraint and limitations, each earning its place.

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?

No output schema exists, yet the description enumerates the returned fields and cardinality, plus error and pagination constraints. For a single-parameter headline tool with no annotations, nothing material 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?

Schema coverage is 100% and the enum is already in the schema, so the baseline is 3. The description goes beyond it by characterizing the accepted values as one of 52 slugs with examples and by specifying the failure mode (400) for other values.

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?

Names a specific verb and resource ("Get Moneycontrol section headlines") and scopes it to a single section's front page. It does not explicitly distinguish itself from siblings like moneycontrol_news or moneycontrol_sections, so it stops short of a 5.

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?

Implicitly tells the agent this is a per-section headline fetch, but never states when to prefer it over moneycontrol_news, moneycontrol_sections, or moneycontrol_article. No exclusions or alternative-selection guidance is given.

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