Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

motleyfool_author

Retrieve a Motley Fool author profile from a canonical author URL, including name, biography, image, and recent investing articles.

Instructions

Get a Motley Fool author profile. Returns a Motley Fool author's name, biography when published, image when available and recent investing articles from their author page. url is required, for example https://www.fool.com/author/2104/. Each article has a title, URL, summary, author, image, type 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": {
      "url": "<url>"
    },
    "name": "motleyfool_author"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical The Motley Fool author URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.7

TDQS

A4.1/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 and does meaningfully disclose the return shape: author name, biography (when published), image (when available), and recent articles with their per-article fields. It does not mention auth needs, rate limits, or pagination of articles, so it is informative but not fully transparent.

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?

Three tight sentences that are front-loaded with purpose, then parameter requirement, then return detail. The final sentence enumerating article fields is slightly list-heavy but earns its place given there is no output schema.

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 simple one-parameter read tool with no output schema, the description adequately covers both input (required URL with example) and output (profile fields plus article fields). Nothing critical is missing for correct invocation, though pagination/limits are unaddressed.

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 single param is already described structurally. The description adds a concrete example URL ('https://www.fool.com/author/2104/') that clarifies the expected format, which is a genuine, if modest, value-add over the schema.

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 a Motley Fool author profile') and immediately clarifies the scope: bio, image, and recent articles from the author page. This clearly distinguishes it from siblings like motleyfool_article, motleyfool_news, or motleyfool_headlines, which surface different Motley Fool resource types.

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 requirement and example format for `url` imply that the agent must already have a canonical author URL, which is useful context. However, there is no explicit when-to-use guidance and no named alternative (e.g., when to use motleyfool_article instead), so usage is only implied.

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