Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sportskeeda_transactions

Fetch complete monthly NFL league or team transactions from the public feed in month-sized windows, avoiding the 10000-row cap. Use month codes to retrieve paginated records.

Instructions

Get complete monthly NFL league or team transactions. Reads the first-party public transaction feed in month-sized windows, avoiding its 10000-row broad-range cap. Discover accepted seasons, months, and team slugs with sportskeeda-transactions-options.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number, 1-1000; default 1
slugNoHost-free page slug; nfl/transactions or an NFL team transactions slug
monthYesMMYYYY month code from transactions-options for the selected season; current live union is listed here
seasonNoSeason start year; current live choices: 2020,2021,2022,2023,2024,2025,2026; defaults to current
per_pageNoRecords per page, 1-500; default 100

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description must carry the behavioral burden, and it usefully explains that the feed is read 'in month-sized windows, avoiding its 10000-row broad-range cap' – a non-obvious constraint that justifies the required month parameter. It omits auth/rate-limit or error behavior, so it is solid but not fully comprehensive.

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 tight sentences: purpose first, mechanism second, discovery tool last. No filler or restatement of the 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 5-parameter read tool with no output schema, the description covers purpose, the windowing constraint, and how to obtain valid enum values. Return format is left unstated but is not strictly required given the missing output schema; overall it is complete enough to invoke correctly.

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 description coverage is 100%, so the schema already documents page, per_page, month, season, and slug semantics. The description's 'month-sized windows' framing reinforces why month matters but adds no syntax or format detail beyond the structured fields, matching the baseline-3 case.

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 ('Get complete monthly NFL league or team transactions') and scopes it to monthly windows. It also names the companion tool (sportskeeda-transactions-options) for discovery, letting an agent distinguish it from the options sibling.

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?

It tells the agent to resolve accepted seasons, months, and team slugs via sportskeeda-transactions-options, which is a real prerequisite/navigation hint. It stops short of explicitly stating when NOT to use this tool versus other sportskeeda feeds.

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