Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

marketwatch_headlines

Fetch current MarketWatch headlines for a chosen section such as markets, investing, or technology, returning titles, URLs, summaries, authors, publication times, and images.

Instructions

Get MarketWatch section headlines. Returns current MarketWatch headlines for one section. section is required and takes latest-news, markets, investing, personal-finance, economy-politics, technology, retirement or real-estate. Each item has its title, URL, summary, author, publication time and image where available.

Input Schema

NameRequiredDescriptionDefault
sectionYesMarketWatch section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.7/5.0
Behavior4/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 useful work: it enumerates the returned fields (title, URL, summary, author, publication time, image) and clarifies that results are scoped to one section. It does not mention pagination, result limits, or freshness, which keeps it from a 5.

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 short sentences, front-loaded with the action and result set. The enum listing duplicates the schema's enum verbatim, which is mild redundancy but not harmful.

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?

No output schema exists, and the description compensates by describing the item fields. For a simple one-parameter read tool this is nearly complete; only pagination/result-count behavior is unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with a single enum parameter fully documented as 'MarketWatch section slug'. The description repeats the enum values, adding no syntax or semantics beyond the schema, so the baseline 3 applies.

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 MarketWatch section headlines') scoped to a single section, which is clear enough to distinguish from the article/author siblings by scope. It does not explicitly differentiate itself from near-neighbors like marketwatch_news or marketwatch_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?

The description says the tool returns headlines 'for one section' and that `section` is required, implying the usage context, but it never states when to prefer this over marketwatch_news, marketwatch_article, or marketwatch_sections, nor that section slugs might come from marketwatch_sections.

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