Skip to main content
Glama

Find individual NFL takes

list_takes
Read-onlyIdempotent

Individual NFL predictions: who made them, when (claimedAt is the publication date), a short excerpt of the wording, the grade (accuracy 0-100, or pending) and the grading arithmetic. Filter by pundit, outlet, prediction type, team, player, season, verdict (hit is 80+, close is 40-79, miss is under 40) and claim dates. 25 rows a page; pass page for more.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_takes"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page of 25 rows.
sortNo
verdictNohit is 80+, close 40-79, miss under 40; graded is any grade.
teamSlugNoOnly takes about this team.
typeSlugNoOnly this prediction type.
outletSlugNoOnly takes published by this outlet.
playerSlugNoOnly takes about this player.
punditSlugNoOnly takes by this pundit.
seasonYearNoOnly takes tied to this NFL season.
claimedAfterNoOnly takes published on or after this date (YYYY-MM-DD).
claimedBeforeNoOnly takes published on or before this date (YYYY-MM-DD).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed40 schema fields changed
    • addedInput schema / properties / claimedAfter / anyOf
      Added value: +[
      +  {
      +    "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedInput schema / properties / claimedAfter / pattern
      Removed value: -"^\\d{4}-\\d{2}-\\d{2}$"
    • removedInput schema / properties / claimedAfter / type
      Removed value: -"string"
    • addedInput schema / properties / claimedBefore / anyOf
      Added value: +[
      +  {
      +    "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedInput schema / properties / claimedBefore / pattern
      Removed value: -"^\\d{4}-\\d{2}-\\d{2}$"
    • removedInput schema / properties / claimedBefore / type
      Removed value: -"string"
    • addedInput schema / properties / outletSlug / anyOf
      Added value: +[
      +  {
      +    "maxLength": 120,
      +    "minLength": 1,
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedInput schema / properties / outletSlug / maxLength
      Removed value: -120
    • removedInput schema / properties / outletSlug / minLength
      Removed value: -1
    • removedInput schema / properties / outletSlug / type
      Removed value: -"string"
    • addedInput schema / properties / page / anyOf
      Added value: +[
      +  {
      +    "maximum": 400,
      +    "minimum": 1,
      +    "type": "integer"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedInput schema / properties / page / maximum
      Removed value: -400
    • removedInput schema / properties / page / minimum
      Removed value: -1
    • removedInput schema / properties / page / type
      Removed value: -"integer"
    • addedInput schema / properties / playerSlug / anyOf
      Added value: +[
      +  {
      +    "maxLength": 120,
      +    "minLength": 1,
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedInput schema / properties / playerSlug / maxLength
      Removed value: -120
    • removedInput schema / properties / playerSlug / minLength
      Removed value: -1
    • removedInput schema / properties / playerSlug / type
      Removed value: -"string"
    • addedInput schema / properties / punditSlug / anyOf
      Added value: +[
      +  {
      +    "maxLength": 120,
      +    "minLength": 1,
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedInput schema / properties / punditSlug / maxLength
      Removed value: -120
    • removedInput schema / properties / punditSlug / minLength
      Removed value: -1
    • removedInput schema / properties / punditSlug / type
      Removed value: -"string"
    • addedInput schema / properties / seasonYear / anyOf
      Added value: +[
      +  {
      +    "maximum": 2100,
      +    "minimum": 2000,
      +    "type": "integer"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedInput schema / properties / seasonYear / maximum
      Removed value: -2100
    • removedInput schema / properties / seasonYear / minimum
      Removed value: -2000
    • removedInput schema / properties / seasonYear / type
      Removed value: -"integer"
    • addedInput schema / properties / sort / anyOf
      Added value: +[
      +  {
      +    "enum": [
      +      "recent",
      +      "oldest",
      +      "best",
      +      "worst",
      +      "skill"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedInput schema / properties / sort / enum
      Removed value: -[
      -  "recent",
      -  "oldest",
      -  "best",
      -  "worst",
      -  "skill"
      -]
    • removedInput schema / properties / sort / type
      Removed value: -"string"
    • addedInput schema / properties / teamSlug / anyOf
      Added value: +[
      +  {
      +    "maxLength": 120,
      +    "minLength": 1,
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedInput schema / properties / teamSlug / maxLength
      Removed value: -120
    • removedInput schema / properties / teamSlug / minLength
      Removed value: -1
    • removedInput schema / properties / teamSlug / type
      Removed value: -"string"
    • addedInput schema / properties / typeSlug / anyOf
      Added value: +[
      +  {
      +    "maxLength": 120,
      +    "minLength": 1,
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedInput schema / properties / typeSlug / maxLength
      Removed value: -120
    • removedInput schema / properties / typeSlug / minLength
      Removed value: -1
    • removedInput schema / properties / typeSlug / type
      Removed value: -"string"
    • addedInput schema / properties / verdict / anyOf
      Added value: +[
      +  {
      +    "enum": [
      +      "all",
      +      "graded",
      +      "hit",
      +      "close",
      +      "miss",
      +      "pending"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedInput schema / properties / verdict / enum
      Removed value: -[
      -  "all",
      -  "graded",
      -  "hit",
      -  "close",
      -  "miss",
      -  "pending"
      -]
    • removedInput schema / properties / verdict / type
      Removed value: -"string"
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), and the description adds real context beyond them: page size of 25, the verdict bucket thresholds, what claimedAt means, and the pending-grade state. It still doesn't disclose default ordering or what happens when all filters are omitted.

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, purpose front-loaded, then return shape, then filters, then pagination – a logical order with little waste. The filter enumeration is dense, and 'the grading arithmetic' is vague phrasing that a reader must decode from context.

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 an 11-parameter, all-optional read tool with no output schema, the description covers return contents, filter semantics, and pagination, which is close to what an agent needs. Missing pieces are limited to sort-value meaning and default behavior with no filters applied.

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 already 91%, so the baseline is 3; the description earns an extra point by clarifying that claimedAfter/claimedBefore are publication-date bounds and by restating the verdict buckets alongside the filter list. The gap is `sort`, whose values (especially 'skill') are explained neither in the schema nor the description.

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 opens with a specific verb+resource ('Individual NFL predictions') and enumerates the returned fields (pundit, date, excerpt, grade, arithmetic), so an agent knows exactly what this returns versus the aggregate-shaped siblings like pundit_record or outlet_record. It stops short of naming those siblings explicitly, which keeps it from a 5.

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?

Usage is only implied: the filter list tells the agent what can be narrowed, and the pagination note tells it how to continue. There is no explicit statement of when to prefer this over pundit_record/leaderboard or any exclusion, so guidance is adequate but inferential.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources