Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

motleyfool_headlines

Retrieve article cards from a specified Motley Fool investing-news section, including titles, URLs, summaries, authors, and publication times for market and stock research.

Instructions

Get The Motley Fool section headlines. Returns the article cards of one Motley Fool investing-news section. section is required: trending-news, news, market-movers, tech-stock-news, market-trends, crypto-news, markets, most-active-stocks, top-stock-gainers or top-stock-losers. Other values return a 400. Items carry the title, URL and, where present, summary, author and publication time.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "section": "<section>"
    },
    "name": "motleyfool_headlines"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectionYesThe Motley Fool section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.7

TDQS

A3.7/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 burden, and it does disclose the return shape (title, URL, optional summary, author, publication time) and error behavior ('Other values return a 400'). It omits auth/rate-limit details, but for a read-only fetch the disclosed behavior is solid.

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?

Front-loaded with purpose, then scope, then the required enum, then the return shape, in three compact sentences. The enum list is somewhat redundant with the schema, costing a little, but nothing is wasted.

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, so the description correctly compensates by enumerating the returned fields, and the single required parameter is fully covered. Absent annotations, additional permission or pagination context would round it out, but it is sufficient to call the tool correctly.

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 the enum fully documented, so the schema does the heavy lifting and baseline 3 applies. The description restates the enum and adds the non-obvious semantics that out-of-enum values return a 400, which is useful but marginal.

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 The Motley Fool section headlines') and clarifies scope ('article cards of one Motley Fool investing-news section'). It does not explicitly name or contrast with siblings like motleyfool_news or motleyfool_sections, but the concept is unambiguous.

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?

Use is implied (pick a section slug, receive its headlines) but there is no explicit when-to-use guidance or comparison to alternatives such as motleyfool_news or motleyfool_sections. The 400-on-invalid-value note helps avoid mistakes but is not routing guidance.

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