Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fanduel_research_projection_tables

Lists FanDuel Research fantasy projection tables by sport and details each table's projection type, position tabs, and scope to identify valid type, position, and scope values.

Instructions

FanDuel Research projection tables. Lists the 17 fantasy projection tables of FanDuel Research (numberFire) for MLB, NBA, NFL, NHL and golf: each table's sport, projection type, the position tabs it offers (with the player positions each tab keeps), whether it takes a scope, a slate or a golf event. Use it to find the valid type, position and scope values for the projections route.

Input Schema

NameRequiredDescriptionDefault
sportNoKeep only this sport's tables

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.2/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 shape of the result: a catalog of 17 tables, each with sport, projection type, position tabs and their retained positions, and whether a scope, slate or golf event is required. It omits read-only/pagination/rate-limit statements, but 'Lists' and the bounded size of the catalog make the read-only nature evident.

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 sentences: what it is, what it returns, and what to use it for — in that order, with zero filler. The purpose is front-loaded before the detailed payload description.

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?

There is no output schema, yet the description adequately conveys the returned fields and the intended discovery workflow, so an agent can plan the call. Minor gap: it doesn't state whether all tables are returned by default when `sport` is omitted, though 'Keep only this sport's tables' in the schema implies that.

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% and the single `sport` enum is fully documented in the schema. The description only echoes the enum values in prose ('MLB, NBA, NFL, NHL and golf') without adding filtering semantics beyond what the schema already says, so baseline 3 applies.

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 ('Lists the 17 fantasy projection tables of FanDuel Research (numberFire)') and enumerates the sports covered. It also spells out what each row contains (sport, projection type, position tabs, scope/slate/golf event), which distinguishes it from the sibling fanduel_research_projections and fanduel_research_projection_slates.

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?

The final sentence gives an explicit call-to-action: use it to discover valid `type`, `position` and `scope` values for the projections route. That is a clear when-to-use cue pointing at the follow-up tool, though it never names an alternative tool explicitly or states when NOT to use it.

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