Skip to main content
Glama

project_custom_prospect

Score a college stat line missing from the database by submitting box-score totals and percentages with model field names; sparse inputs may abstain or return low confidence.

Instructions

Score a college stat line that isn't in the database, e.g. a current prospect you found elsewhere. Provide college box-score totals/percentages using the same field names as the model (Games, Minutes_Per_Game, FG, FGA, FG%, 3P, 3PA, 3P%, FT, FTA, FT%, TRB, AST, STL, BLK, TOV, PTS, TS%, eFG%, TRB%, AST%, STL%, BLK%, TOV%, USG%, OWS, DWS, WS, WS/40, LastConf). Missing fields are treated as 0 and count toward the abstain rule, so this will usually abstain or run low confidence on a sparse stat line. That's the trust layer working as intended, not a bug.

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": {
      "stats": "<stats>"
    },
    "name": "project_custom_prospect"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoCustom prospect
statsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does disclose important traits: missing fields are treated as 0, that affects the abstain rule, and sparse inputs usually yield abstention or low confidence as a deliberate trust-layer behavior. It does not describe the return shape, permissions, determinism, or rate limits, so the disclosure is substantive but not complete.

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 definition is front-loaded with the main purpose, followed by the required field list and then the important abstain caveat. It is efficient overall, though the long inline field enumeration is dense and could be more scannable if formatted as a structured list.

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?

Given the lack of annotations, output schema, and schema descriptions, the definition covers the core invocation details and the key behavioral caveat about sparse stat lines causing abstention or low confidence. It leaves some gaps around what the score output actually contains and how the optional name parameter is used, but it is largely complete for calling the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the input schema only defines a free-form numeric stats object, so the description adds essential semantics by listing the exact accepted field names and stating that missing fields default to 0. The optional name parameter is not explained, but the core stats parameter is substantially specified beyond the schema.

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?

The description uses a specific verb and scope: "Score a college stat line that isn't in the database." The phrase "e.g. a current prospect you found elsewhere" clearly frames this as the custom/external-prospect path, distinguishing it from database lookup or comparison tools even without naming a sibling.

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 a clear when-to-use condition: a stat line not already in the database, such as a prospect found elsewhere. It does not explicitly say when not to use it or name alternatives like search_players or compare_prospects, so exclusions and routing guidance are incomplete.

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