Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

marketwatch_news

Retrieve MarketWatch top stories without parameters and get title, URL, summary, author, publication time and image for each. Use marketwatch-headlines for a single section.

Instructions

Get MarketWatch top stories. Returns MarketWatch's current top stories, with no parameters. Each item has its title, URL, summary, author, publication time and image where available. Use marketwatch-headlines to read a single section instead.

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 burden. It discloses that the call takes no parameters and enumerates the returned fields (title, URL, summary, author, publication time, image where available), which is meaningful since there is no output schema. It does not mention result count, pagination, or freshness/caching behavior.

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 short sentences: purpose first, return payload second, sibling routing last. Every sentence carries information and none is redundant with structured fields.

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?

With no annotations and no output schema, the description compensates by describing both the scope of the call and the shape of each returned item. An agent has everything it needs to call this correctly and interpret the result.

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 states that explicitly ('with no parameters'), so there is nothing further to document. Baseline for a 0-param tool is 4.

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 MarketWatch top stories') and pins the scope as the site-wide top-stories feed rather than a section feed. It also pre-empts confusion with the similarly named `marketwatch_headlines`/`marketwatch_sections` siblings by explicitly contrasting the two.

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?

It names an alternative and the condition that selects it: 'Use `marketwatch-headlines` to read a single section instead.' That gives clear routing context, though only one of the several MarketWatch siblings is addressed and there is no explicit 'when not to use' for article/author lookups.

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