Skip to main content
Glama

rescore_match

Re-run highlight scoring and curation on an already analyzed match without rereading the demo, keeping existing highlight IDs, videos, and hand-picked featured plays.

Instructions

Re-run the highlight scoring and curation on a match that is already analyzed (fast, the demo is not read again). Highlights keep their ids and videos; featured plays chosen by hand are kept.

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": {
      "match_id": "<match_id>"
    },
    "name": "rescore_match"
  }
}

Input Schema

NameRequiredDescriptionDefault
match_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Beyond the annotations (not read-only, not destructive, not open-world), the description discloses meaningful behavior: it is fast because the demo is not re-read, highlight ids and videos are preserved, and hand-picked featured plays survive the re-run. That preservation/idempotency detail is exactly the kind of context annotations cannot carry.

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?

Two tight sentences, no filler. The speed rationale is front-loaded in the parenthetical and the preservation guarantees follow immediately after.

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 present, return values need not be explained, and the annotations cover the safety profile. The description covers cost, data preservation, and the prerequisite match state; only the match_id format and failure behavior for unanalyzed matches are left unstated.

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?

There is one parameter (match_id) with 0% schema description coverage, and the description only implies it via 'on a match that is already analyzed'. No format, id source, or validation detail is added, so it does not fully compensate for the bare schema.

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 states a specific verb and resource: re-run highlight scoring and curation on an already-analyzed match. The parenthetical 'the demo is not read again' implicitly distinguishes it from the heavier produce/import path, so an agent can separate it from produce_match, though no sibling is named explicitly.

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 gives the key precondition ('a match that is already analyzed'), which is the deciding factor for using this instead of a full produce. It does not name the alternative tool for unanalyzed matches or state exclusions, which keeps it below a 5.

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