Skip to main content
Glama

My saved targets

invoke_my_targets

Added after you connected: the first call asks you to approve it. The user's saved BankrollSZN Targets. action tonight (default) lists every saved target with the players who qualify on today's slate (NBA and NHL today, NFL this week), with projection, salary and the trait values. action list shows saved targets with their backtest summary. action save saves a backtest as a target: pass the same arguments as backtest_draft_target plus an optional label (free plan 3 active targets, Fan 25). action delete removes one by id. Saved targets also show on https://bankrollszn.com/targets.

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": "invoke_my_targets"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoTarget id for delete.
maxNoMaximum season trait values. Same keys as min.
minNoMinimum season trait values. NBA: pullup_share, catch_shoot_share, drop_killer, switch_killer, roll_threat, mins. NFL: target_share, air_yards_share, wopr, rush_share, targets_pg, carries_pg, pass_att_pg, ppr_pg. NHL: toi_pg, pp_toi_pg, shots_pg, points_pg, blocks_pg, dk_pg. MLB: iso, avg, slg, k_rate, bb_rate, hr_rate, sb_pg, dk_pg, pa. Shares as fraction or percent.
batsNoMLB only: L, R, S.
labelNoName for a saved target.
limitNoMax games in the game list. The plan limit applies.
sportNoSport.
zonesNoNBA only. Shot-zone share of the player's FGA: Restricted area, Paint (non-RA), Mid-range, Corner 3, Above the break 3.
actionNoDefault tonight.
seasonNoSeason. NBA and NHL 2025-26 style, NFL and MLB a year. Defaults: NBA 2025-26, NHL 2025-26, NFL 2025, MLB 2026 (the last full season). The current season works too.
defenseNoThe defense to test against: team abbreviation (NBA ORL, NY; NFL MIA, LA; NHL SJS; MLB COL means hitters vs that team's pitching).
playersNoLimit to these player names.
primaryNoStat the game list is graded on. NBA pts (default), pts36, fga, reb, ast, tpm, pra, ts, dk, min. NFL ppr (default), tgt, rec, recyd, car, rushyd, scrim, td, passyd. NHL dk (default), sog, pts, blk, sb, toi. MLB dk (default), h, tb, hr, rrbi, k.
min_gamesNoMinimum games in the season for a player to count (baseline sample). Defaults NBA 5, NFL 3, NHL 5, MLB 10.
positionsNoNBA G, F, C. NFL QB, RB, WR, TE. NHL C, L, R, D, or F for all forwards. MLB C, 1B, 2B, 3B, SS, LF, CF, RF, DH, OF, IF.
play_typesNoNBA only. Play-type share of the player's possessions (stats.nba.com Synergy). type: PnR ball handler, PnR roll man, Isolation, Transition, Spot up, Handoff, Post up, Off screen, Cut, Putback, Misc (short names like iso or pnr work). min and max as a fraction (0.12) or percent (12).
size_groupsNoNBA only: c7 (7-0 and up), big (6-9 to 6-10), wing, small (6-5 and under).
min_thresholdNoGame inclusion threshold. NBA minutes (default games over 24 min), NHL TOI minutes (default 10), NFL opportunities (default 1), MLB plate appearances (default 3).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

The description adds real context the annotations don't: the first call triggers an approval prompt, free plan caps active targets at 3 (Fan 25), and the plan limit applies to the game list. However, it never says that delete is irreversible or what happens to a saved target when a save collides with an existing label, and it does not describe the return shape for tonight/list. Note also a mild tension: action delete removes a saved target while annotations declare destructiveHint=false, which an agent could misread as no data loss being possible.

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?

The text is information-dense and front-loads the default action before covering the remaining three branches, with no filler sentences. It is slightly disorganized: the first sentence is a fragment about saved targets, the approval note is wedged in front of it, and the trailing URL adds little for an agent. Still efficient for four actions.

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 tool with 18 parameters, four actions and no output schema, the description covers every action branch, the save parameter delegation to backtest_draft_target, the plan quota, and roughly what tonight and list return (projection, salary, trait values; backtest summary). Missing pieces are the delete confirmation/irreversibility behavior and any hint about response structure for save/delete, which prevents a 5.

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 id, min/max trait keys, zones, play_types, primary, season defaults and min_threshold. The description's only genuine addition is that save accepts the same arguments as backtest_draft_target plus an optional label, which links the 18 loosely-scoped parameters to a known sibling. It adds no syntax or format detail beyond what the schema states, so the baseline 3 applies.

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 names the resource (the user's saved targets) and enumerates all four actions with a specific verb per action: tonight lists qualifiers, list shows backtest summaries, save persists a backtest, delete removes by id. It also distinguishes itself from the sibling backtest_draft_target by saying save takes 'the same arguments as backtest_draft_target plus an optional label'. It falls short of a 5 because the leading sentence is about an approval prompt rather than purpose, and the multi-action scope makes the single-sentence purpose ('My saved targets') ambiguous about which action is default until later in the text.

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?

Each action carries an explicit condition: tonight is marked as the default and is tied to today's slate, list is for viewing backtest summaries, save is for persisting a backtest as a target, delete requires an id. That is effectively when-to-use guidance per branch. It does not state when NOT to use the tool or explicitly redirect to alternatives for building a backtest versus saving one, which keeps it below 5.

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