Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

sportskeeda_transactions

Read-only

Get complete monthly NFL league or team transactions from the site's public feed. Supply a month from sportskeeda_transactions_options, with an optional host-free team transactions slug and pagination.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "month": "<month>"
    },
    "name": "sportskeeda_transactions"
  }
}

Input 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. Documented values: 022020, 032020, 042020, 052020, 062020, 072020, 082020, 092020, 102020, 112020, 122020, 012021, 022021, 032021, 042021, 052021, 062021, 072021, 082021, 092021, 102021, 112021, 122021, 012022, 022022, 032022, 042022, 052022, 062022, 072022, 082022, 092022, 102022, 112022, 122022, 012023, 022023, 032023, 042023, 052023, 062023, 072023, 082023, 092023, 102023, 112023, 122023, 012024, 022024, 032024, 042024, 052024, 062024, 072024, 082024, 092024, 102024, 112024, 122024, 012025, 022025, 032025, 042025, 052025, 062025, 072025, 082025, 092025, 102025, 112025, 122025, 012026, 022026, 032026, 042026, 052026, 062026, 072026, 082026, 092026.
seasonNoSeason start year; current live choices: 2020,2021,2022,2023,2024,2025,2026; defaults to current. Documented values: 2020, 2021, 2022, 2023, 2024, 2025, 2026.
per_pageNoRecords per page, 1-500; default 100

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / month / description
      Added value: +"MMYYYY month code from transactions-options for the selected season; current live union is listed here. Documented values: 022020, 032020, 042020, 052020, 062020, 072020, 082020, 092020, 102020, 112020, 122020, 012021, 022021, 032021, 042021, 052021, 062021, 072021, 082021, 092021, 102021, 112021, 122021, 012022, 022022, 032022, 042022, 052022, 062022, 072022, 082022, 092022, 102022, 112022, 122022, 012023, 022023, 032023, 042023, 052023, 062023, 072023, 082023, 092023, 102023, 112023, 122023, 012024, 022024, 032024, 042024, 052024, 062024, 072024, 082024, 092024, 102024, 112024, 122024, 012025, 022025, 032025, 042025, 052025, 062025, 072025, 082025, 092025, 102025, 112025, 122025, 012026, 022026, 032026, 042026, 052026, 062026, 072026, 082026, 092026."
    • addedInput schema / properties / page / description
      Added value: +"Page number, 1-1000; default 1"
    • addedInput schema / properties / per_page / description
      Added value: +"Records per page, 1-500; default 100"
    • addedInput schema / properties / season / description
      Added value: +"Season start year; current live choices: 2020,2021,2022,2023,2024,2025,2026; defaults to current. Documented values: 2020, 2021, 2022, 2023, 2024, 2025, 2026."
    • addedInput schema / properties / slug / description
      Added value: +"Host-free page slug; nfl/transactions or an NFL team transactions slug"
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and external-feed nature are covered. The description adds that the data comes from the site's public feed and that pagination is available, but says nothing about rate limits, freshness, or result ordering beyond what annotations and the output schema provide.

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?

Two sentences that are front-loaded with the action and resource, followed by the parameter guidance. Every clause carries information; no filler.

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 an output schema, annotations, and complete parameter coverage, the description only needs to orient the agent, which it does. It is essentially complete for a read-only feed tool, though a note on coverage or update cadence would fully close the gap.

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 month, slug, page, per_page and season in detail, including the valid month codes and the reference to transactions-options. The description's mention of the options tool duplicates what the schema's month description already states, adding no new semantics, so baseline 3 is appropriate.

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 ('Get'), resource ('monthly NFL league or team transactions'), and scope ('from the site's public feed'), and the slug option makes clear it can return either league-wide or team-level data. An agent can distinguish this from the companion sportskeeda_transactions_options tool 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?

Gives a clear prerequisite: supply a month obtained from sportskeeda_transactions_options, and notes the slug and pagination are optional. It does not state when-not to use the tool or name a competing sibling for broader sports data, but the context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources