Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fanduel_research_featured_articles

Retrieve the curated featured FanDuel Research articles for a chosen sport, including titles, authors, publish times, links and tags, to surface editor picks instead of the latest feed.

Instructions

FanDuel Research featured articles. Returns the articles the FanDuel Research editors feature on a sport's page (about ten per sport, such as the week's best bets for the NFL), each with title, description, author, publish time, link and tags. It is a curated list, not the newest-first feed of the articles route: for most sports it differs from the latest articles. A sport with nothing featured (Women's Soccer and Sports Betting 101 on 2026-10-24) returns an empty list. The service has no homepage variant, so sport is required.

Input Schema

NameRequiredDescriptionDefault
sportYesSport or topic slug from the `sports` route

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.3/5.0
Behavior4/5

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

No annotations, so the description carries the burden and does so well: it discloses the returned fields (title, description, author, publish time, link, tags), the approximate cardinality (~10 per sport), and the empty-list edge case with a concrete example. What it omits is operational context such as pagination, caching, or rate limits, which keeps it from a 5.

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?

Four sentences, front-loaded with what the tool returns before moving to differentiation and edge cases; nothing is redundant. The parenthetical with an exact date ('Women's Soccer and Sports Betting 101 on 2026-10-24') is slightly over-specific but does illustrate the empty case concretely.

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?

With no output schema and no annotations, the description supplies the return shape, item count, empty-result behavior, and the required-parameter rationale — enough for an agent to call it correctly and interpret an empty response. The only gap is that the tags/field types and any pagination are left 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 enum's own description already points at the `sports` route, so the schema does the heavy lifting. The description adds value by explaining *why* `sport` is mandatory ('The service has no homepage variant'), which tells the agent not to attempt a call without it.

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 ('Returns the articles the FanDuel Research editors feature on a sport's page') and quantifies the volume ('about ten per sport'). It explicitly distinguishes itself from the sibling `articles` route by calling this a 'curated list, not the newest-first feed', so an agent can pick between the two without opening either schema.

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?

Names the alternative (`articles` route) and the condition that separates them ('for most sports it differs from the latest articles'), plus a constraint that selects the parameter ('no homepage variant, so `sport` is required'). It stops short of an explicit directive like 'use X when you want latest news', leaving the final choice to inference.

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