Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fanduel_research_authors

Fetch pages of FanDuel Research authors with IDs, bios, social accounts, and sport or topic coverage; filter by sport and paginate with a cursor.

Instructions

FanDuel Research authors. Returns a page of FanDuel Research authors with their id, slug, bio, social accounts and the sports and topics they write for. Filter by sport; page with cursor while has_more is true. The author id filters the articles route.

Input Schema

NameRequiredDescriptionDefault
limitNoAuthors per page, 1 to 50; default 20
sportNoSport or topic slug from the `sports` route
cursorNoContinue from the previous response's `next_cursor`

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations and no output schema, the description carries the burden and does disclose the payload shape and the pagination contract (`has_more` / `next_cursor`), which is genuine behavioral context. It omits anything about auth, rate limits, or result ordering, but for a read-only listing those gaps are minor.

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?

Three short sentences, front-loaded with what the tool returns before the operational detail. No filler and nothing repeated from the schema verbatim.

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 three-parameter, optional-only listing tool with no annotations and no output schema, the description covers what comes back and how to page through it, which is the core need. The only shortfall is that the relationship to the singular author-detail sibling is left implicit.

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%, so the baseline is 3; the description goes past the schema by explaining the paging loop (`cursor` until `has_more` is false) and by cross-referencing the `sports` route as the source of valid sport slugs. It stops short of explaining default page sizes or what happens on invalid cursors, so it is not a 5.

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 states a specific resource (FanDuel Research authors) and enumerates the returned fields (id, slug, bio, social accounts, sports/topics). It implicitly distinguishes itself from the singular `fanduel_research_author` detail route and from `fanduel_research_articles` by noting the id linkage, but it never explicitly says 'this lists many authors; use fanduel_research_author for one author'.

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?

It gives concrete operational guidance — filter by sport, page with `cursor` while `has_more` is true — and mentions that the returned author `id` feeds the `articles` route. However, it never states when to pick this tool over the sibling `fanduel_research_author`, so the alternative selection 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