Skip to main content
Glama

Scout Team

scout_team
Read-only

Analyze a club's tactics across recent games or a chosen season, using team, match types, and locations. Intended only for explicit scouting requests.

Instructions

Scout a club's tactics over its recent games. Use only when explicitly asked to scout a team. Give last_games (1-30, default 10) OR season, not both. Some information might require a supporter subscription.

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": {
      "team_id": "<team_id>",
      "match_types": "<match_types>",
      "locations": "<locations>"
    },
    "name": "scout_team"
  }
}

Input Schema

NameRequiredDescriptionDefault
seasonNo
team_idYes
locationsYes
last_gamesNo
match_typesYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only supply readOnlyHint=true, so the description adds real value: it discloses that 'some information might require a supporter subscription', an entitlement gate the agent otherwise could not anticipate, and it prevents an invalid parameter combination. It doesn't say whether partial data is returned silently when unsubscribed, which would be the final piece.

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?

Three short sentences, each doing distinct work: purpose, usage restriction, parameter rule, and entitlement caveat. The usage restriction is front-loaded before the parameter mechanics, which is the right ordering.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 no explanation, and the entitlement and mutual-exclusion notes are the highest-value additions. But for a tool whose schema is 0% documented, leaving three required parameters — including two enum arrays — completely unglossed is a real gap; an agent gets no hint about what match_types filtering means for the analysis scope.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the full burden, yet it only addresses two of five parameters. It does add genuine meaning for last_games (range 1-30 and default 10 are absent from the schema's bare integer type) and captures the season/last_games mutual exclusion that the schema cannot express. The three required parameters — team_id, match_types, and locations — receive no explanation at all.

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?

'Scout a club's tactics over its recent games' names a specific verb (scout) and a specific resource (a club's tactical profile across recent matches), which is meaningfully distinct from the roster/stats/schedule siblings. It stops short of saying what a 'scout' output contains, so an agent must infer that from the output schema.

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?

'Use only when explicitly asked to scout a team' is a genuine negative-use guardrail that will stop an agent from substituting this for get_team_stats. The last_games OR season exclusivity is stated explicitly. What's missing is any positive routing (e.g. which sibling to use when the user just wants aggregate stats).

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