Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

motleyfool_sections

List the 10 Motley Fool stock market news section slugs accepted by the headlines endpoint, including names and URLs for each section.

Instructions

List The Motley Fool news sections. Lists the 10 Motley Fool Stock Market News section slugs that the headlines endpoint accepts, from trending-news and news to most-active-stocks, top-stock-gainers and top-stock-losers. Each entry has a slug, a display name (news is named Stock News) and a section url.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.7

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden but discloses key behavior: a fixed set of 10 entries and the three fields each entry returns (slug, name, url), including the naming quirk that `news` is displayed as Stock News. It does not explicitly state read-only or rate-limit behavior, but 'List' plus the field disclosure covers the essentials for a static lookup.

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?

Purpose is front-loaded in the first sentence, followed by supporting detail. It is efficient overall, though the enumeration of example slugs is somewhat listy and could be trimmed without losing meaning.

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, so the description's disclosure of the returned fields is doing real work. For a zero-parameter static list tool this is close to complete; only explicit read-only/pagination context is absent, which is minor here.

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, so there is nothing to disambiguate; baseline is 4. The description instead documents the return values, which is the only semantic content available.

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 (List) and resource (The Motley Fool news sections) and scopes it precisely as the 10 Stock Market News section slugs accepted by the headlines endpoint. This clearly distinguishes it from siblings like motleyfool_headlines, motleyfool_news and motleyfool_article.

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 ties itself to a consumer: the slugs 'that the headlines endpoint accepts', which tells an agent to call this before motleyfool_headlines to obtain valid section values. It stops short of an explicit when-not-to-use or naming the sibling tool by name.

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