Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

marketwatch_sections

Lists valid MarketWatch sections with their slug, display name, and URL so you can choose the correct category for marketwatch-headlines requests.

Instructions

Get MarketWatch sections. Lists the eight MarketWatch sections accepted by marketwatch-headlines: latest-news, markets, investing, personal-finance, economy-politics, technology, retirement and real-estate. Each entry has a slug, display name and section url.

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, and it delivers by disclosing the exact cardinality (eight sections) and the returned field shape (slug, name, url). It omits auth/rate-limit notes, but for a zero-parameter read-only enumeration that carries little risk.

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?

Two sentences, front-loaded with the purpose, then the payload contents. The long slug list is functional rather than filler, and nothing is repeated.

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?

There is no output schema, and the description compensates by describing the entry structure and count. For a trivial lookup tool with no parameters, an agent has everything needed to call it and consume 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, which sets the baseline at 4. The description still adds value by naming the concrete slug values an agent will pass downstream to marketwatch-headlines.

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+resource ('Get MarketWatch sections') and enumerates the eight slugs returned, then ties them to the consuming sibling marketwatch-headlines. An agent can distinguish this from the many other *_sections tools by the site scope alone.

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?

Explicitly frames the tool as the source of the values accepted by `marketwatch-headlines`, which effectively tells the agent when to call it and what to do with the result. There is no explicit when-not or exclusion, so it stops short of a full 5.

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