Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

moneycontrol_news

Retrieve 50 recent Moneycontrol news stories across all sections, newest first, excluding videos, podcasts, galleries, and sponsored posts.

Instructions

Get Moneycontrol latest news. Returns the 50 newest Moneycontrol stories across all sections, newest first, with no parameters. Each item has title, url, published_at (RFC3339 UTC) and image_url. Videos, podcasts, photo galleries and sponsored brand-connect posts are left out.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the exact result count (50), ordering (newest first), content exclusions (videos, podcasts, galleries, sponsored posts), and the shape/format of returned items including RFC3339 UTC timestamps. It stops short of noting auth, rate limits, or freshness/refresh behavior.

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 tight sentences, front-loaded with purpose before the count/order and field details. Every sentence adds information (scope, exclusions, return fields), with no filler or repetition.

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?

There is no output schema and no annotations, so the description must supply the return contract; it does so precisely (field names, timestamp format, item count, ordering, exclusions). For a parameterless feed tool this is close to complete, with only auth/error behavior left unspecified.

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 and the description explicitly confirms 'with no parameters', matching the empty schema. Baseline 4 applies since there is nothing to document beyond confirming the no-argument contract.

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 Moneycontrol latest news') and adds scope ('across all sections', 50 newest, newest first), which hints it is unfiltered. However, it never names or distinguishes itself from close siblings like moneycontrol_headlines or moneycontrol_article, so an agent cannot fully disambiguate from the text alone.

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?

Usage is only implied by 'latest news'; there is no explicit statement of when to pick this over moneycontrol_headlines, moneycontrol_sections, or moneycontrol_article. No exclusions or prerequisites are given, leaving the routing decision to inference.

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