Skip to main content
Glama

get_model_card

Retrieve the NBA draft-scouting model card to review data coverage, features, per-skill accuracy, and known limitations before relying on predictions.

Instructions

The model card: data coverage, features, per-skill accuracy, and known limitations. Also available as the scout://model-card resource.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations exist, but this is a zero-parameter read of a documentation artifact, so the behavioral burden is light. The description usefully discloses that the same content is exposed as a resource, letting the agent avoid a redundant call; it says nothing about whether the card is static or regenerated per request.

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, front-loaded with the resource identity, followed by the content enumeration and the resource alternative. The colon-fragment opening is slightly clipped but every clause carries information.

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 no output schema, the enumeration of the card's contents effectively doubles as a return-value description, which is enough for an agent to decide whether the call answers its question. It could add whether the card reflects current data or is fixed documentation.

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?

The tool takes no parameters, so there is nothing to disambiguate; baseline 4 applies. The description correctly spends no words on parameters.

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 a specific artifact (the 'model card') and enumerates its contents — data coverage, features, per-skill accuracy, known limitations — so an agent knows exactly what it retrieves. It does not explicitly distinguish itself from closer siblings like get_skill_profile or explain_tier, 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: an agent infers it should call this to understand the underlying model. The one routing hint given is a delivery-mechanism alternative (`scout://model-card` resource), not a when-to-use-this-vs-that-tool rule, and no sibling is named or excluded.

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