Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

moneycontrol_article

Fetch public Moneycontrol article content and metadata from a canonical URL. Pro subscriber stories return 403; live blogs return one paragraph per update.

Instructions

Get Moneycontrol article content. Returns public Moneycontrol article metadata and body paragraphs from a canonical article URL. Moneycontrol Pro subscriber stories are refused with a 403 permission error because no free content is available. Live blogs return one paragraph per update.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesCanonical Moneycontrol article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.2/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 and does meaningful work: it discloses the 403 refusal for Pro content and the one-paragraph-per-update behavior of live blogs. It does not address rate limits or auth, but for a public read-only article fetcher the key failure modes are covered.

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 compact sentences front-load the action and output, then add caveats. 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?

The description is sufficient for a one-parameter article fetch: it defines input, output, a failure case, and a special output format. Absence of an output schema makes a bit more return-structure detail desirable, but the tool is still safely callable from this definition.

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 single parameter is already well documented in the schema (100% coverage). The description reinforces 'canonical' and adds a public-content restriction that helps the agent avoid paywalled URLs, exceeding the schema's bare definition but not substantially.

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?

The opening 'Get Moneycontrol article content' names a verb, resource, and source, and the following sentence specifies the return scope (metadata and body paragraphs) and input type. This clearly distinguishes it from Moneycontrol author/headlines tools and from other publishers' article tools.

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?

The description conveys that it is for public canonical Moneycontrol articles and warns that Pro stories will fail, which implies the correct usage envelope. It does not explicitly route the agent to alternative Moneycontrol tools (e.g., moneycontrol_headlines, moneycontrol_sections) or state when to prefer them, leaving selection partly 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