Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fanduel_sportsbook_trending

Retrieve FanDuel Sportsbook trending search terms, optionally resolving each to its event, competition, and entity details for market monitoring.

Instructions

FanDuel Sportsbook trending searches. Returns the terms the Sportsbook's search box shows as trending (about ten players, teams and clubs). With enriched=true each term is resolved to the event it points at, with the competition, event name and id, entity type (for example PLAYER), image and the time the entry expires. The list was identical in every market tested, so the route takes no state.

Input Schema

NameRequiredDescriptionDefault
enrichedNoResolve each term to its event, competition and entity; default false

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does well: it makes clear this is a read operation ('Returns'), gives the approximate list size, explains the enriched payload fields, and notes that the list is identical across markets so no state is taken. It does not discuss rate limits or response volatility, but those are minor for this endpoint.

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?

The description is front-loaded with the core purpose, then covers enriched behavior and market invariance in three tight sentences. Every sentence adds useful understanding and none is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter tool with no output schema but full schema coverage, the description explains both the basic return (trending terms) and the enriched return shape. It also explains why there are no location or market parameters, which is exactly the context an agent needs.

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 already documents the enriched boolean and its default. The description adds meaningful detail beyond the schema by enumerating what enriched resolves each term to: competition, event name and id, entity type, image, and expiration time.

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?

The description clearly states a specific resource: the terms FanDuel Sportsbook's search box shows as trending, including their approximate composition (players, teams, clubs). It does not name a sibling tool such as fanduel_sportsbook_search, so sibling differentiation is implied rather than explicit.

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 description implies when to use the tool by describing it as trending search terms and by explaining the enriched mode. However, it gives no explicit when-to-use guidance relative to alternatives like fanduel_sportsbook_search or autocomplete, and no exclusions are 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