Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

motleyfool_article

Fetch a Motley Fool investing article by canonical URL and return structured JSON with title, authors, dates, body paragraphs, image, and paywall status.

Instructions

Get a Motley Fool article. Returns one Motley Fool investing article by url, which must look like https://www.fool.com/investing/YYYY/MM/DD/slug/; only public /investing/ URLs are accepted. The response has the title, description, section, authors, publication and update times, image URL, body paragraphs and a paywalled flag.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical The Motley Fool investing article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.7

TDQS

A4.2/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 well: it discloses the exact return shape (title, description, section, authors, publication and update times, image URL, paragraphs, paywalled flag) and a key behavioral constraint (only public /investing/ URLs; a paywall flag exists). It omits auth/rate-limit behaviour, but the substantive disclosure is strong.

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 dense sentences with no filler, front-loading the purpose before the URL constraint and the return shape. Every clause adds operational information.

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 must describe the response, and it does so comprehensively (field list plus paywalled flag). Nothing needed to call or interpret the result is missing; only minor auth/error behaviour is unstated.

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?

Schema coverage is 100% and the schema only says 'Canonical The Motley Fool investing article URL'. The description adds real value beyond that by specifying the required URL pattern (https://www.fool.com/investing/YYYY/MM/DD/slug/) and the public-only restriction, so an agent can validate its input before calling.

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 a Motley Fool article') and scopes it to a single article by URL, sharply distinguishing it from siblings like motleyfool_news, motleyfool_headlines, and motleyfool_sections. An agent can tell at a glance this retrieves one article, not a list.

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 URL format constraint and 'only public /investing/ URLs are accepted' implicitly define when the tool applies, but there is no explicit when-to-use guidance or pointer to alternatives (e.g., use motleyfool_news for listings). Usage is inferable rather than stated.

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