Muffed

View saved version →

---
name: muffed-figures
description: How to quote Muffed's verified NFL figures correctly. Use whenever a Muffed tool returns data — query_stat_leaders, get_entity_metrics, compare_entities, get_metric_definition, list_metrics, verify_claim, get_backfield, run_stat_query, or any sleeper_* tool — or when answering an NFL or fantasy-football question using Muffed figures. Covers quoting the pre-formed sentence, the difference between verified and computed figures, carrying attribution verbatim, honouring disclosures and season coverage, and the no-advice boundary.
when_to_use: A Muffed MCP tool has returned a response; the user asks about NFL stats, a player's or team's season, a backfield, a computed statistic, or a Sleeper league; the user states a football figure that should be checked.
---

# Working with Muffed's verified figures

Muffed serves NFL figures that were verified against a gated panel before they
were published. The value is not that the numbers exist — it is that each one
arrives with the rank its source gave it, the population it was ranked against,
its own attribution, and an as-of date. Handling a response carelessly throws
away the only thing that makes it better than a guess.

These are the house rules. They exist because each one has a specific way of
going wrong.

## 1 · Quote `verified_sentence`

Every successful response from a verified tool carries `verified_sentence`: a
complete, already attributed claim built from the returned row.
(`run_stat_query` is the exception — see rule 2.)

> "No one posted more rush yards over expected than James Cook with 358.16 in
> 2025, 1st of 49 (Data via nflverse · NFL Next Gen Stats via nflverse)."

Quote it. Do not rebuild the same claim from the individual fields — that is
where a rank gets attached to the wrong figure, or a season to the wrong number.
The sentence has already related them correctly.

The prose block at `content[0]` is written to be read aloud and is safe to use
directly. `values{}` carries every figure in it, exact and unrounded, when you
need more precision than the prose shows.

## 2 · Computed figures are a different class from verified ones

Two classes of figure come off this server and they are not interchangeable.
Most tools return figures that were verified before they were published: those
carry `verified_sentence` and a citation that says verified. `run_stat_query`
computes a figure on request instead, for questions the panel holds no
pre-computed row for — qualified superlatives, multi-season spans, derived
rates.

Its responses carry **`computed_sentence` rather than `verified_sentence`**, a
`method` block naming the population, the measure and the query shape, and the
`computed_not_verified` disclosure, which fires on every one of them.

Quote `computed_sentence` for those, exactly as rule 1 says to quote
`verified_sentence`. Where it could matter to a reader, say the figure was
computed on request rather than drawn from the verified panel.

- **Right:** "Muffed computed this on request: ...  (method: ...)"
- **Wrong:** presenting it as "Muffed's verified figure", or quoting it beside a
  `verified_sentence` with nothing to tell the two apart.

The difference between the two is the thing this service is for; presenting one
as the other gives away the only claim it makes.

## 3 · Carry `attribution` verbatim

The `attribution` string is licence text, not a courtesy. Reproduce it whole:

- **Right:** `Data via nflverse · NFL Next Gen Stats via nflverse`
- **Wrong:** "nflverse data", "Source: nflverse", "via nflverse"

Shortening it drops credit the CC-BY licence requires. Where a response carries
the `share_alike` disclosure, the figures are CC-BY-SA and the same applies with
more force.

## 4 · Do not compute figures of your own

This is the caller's side of rule 2. `run_stat_query` is where the server
computes something on request and labels it; everything below is about numbers
you worked out yourself, which carry no label at all.

Preview of the first 4,000 characters. Read full instructions →