Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

motleyfool_news

Fetch up to 50 recent Motley Fool investing stories, newest first, with title, URL, and publication time. Use for finance research and headline tracking.

Instructions

Get The Motley Fool top investing stories. Returns up to 50 recent Motley Fool investing stories, newest first, each with its title, URL and publication time. Only stories at /investing/YYYY/MM/DD/slug/ URLs are included. It takes no parameters; use the headlines endpoint for a named section.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.7

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose real behavior: cap of up to 50 stories, newest-first ordering, the fields returned (title, URL, publication time), and the URL-pattern inclusion rule. No auth, rate-limit, or failure-mode context is given, keeping it out of the top band.

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 sentences, front-loaded with purpose then behavior then the sibling redirect. No filler, no repetition of the tool name.

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?

For a zero-param feed with no output schema or annotations, the description covers what is returned, how much, in what order, and which URLs qualify. Minor gaps remain (freshness/caching, whether the list is paginable beyond 50), but nothing an agent needs to call it correctly is missing.

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?

Zero parameters, so the baseline is 4; the description confirms 'It takes no parameters', which is consistent with the empty schema and leaves no ambiguity.

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?

Specific verb (Get) plus resource (The Motley Fool top investing stories) with explicit scope and return content. It also states the URL-pattern constraint (/investing/YYYY/MM/DD/slug/) that separates it from the article/headlines siblings.

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 explicitly says it takes no parameters and routes the agent to 'the headlines endpoint for a named section', which is a real when-not condition naming an alternative. It doesn't distinguish itself from motleyfool_headlines/motleyfool_sections more fully, so it stops short of a 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