Skip to main content
Glama

Footalytics

get_team

Team profile from the Footalytics ratings table: current rating, games tracked and league (1 credit per successful call).

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_team"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoTeam name in English, e.g. Arsenal. Chinese names do not resolve.
limitNoOptional, default 20, max 50
leagueNoOptional league filter (eng.1 or premier-league)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does add real value by disclosing the data source (ratings table) and the cost model (1 credit per successful call). It says nothing about failure modes — notably that Chinese names do not resolve, a detail buried in the schema rather than the description — nor about whether a miss still consumes credit.

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?

A single tight sentence with the resource and return fields front-loaded and cost appended. No wasted wording, though the parenthetical cost clause slightly interrupts the field enumeration.

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?

For a simple read lookup the description covers outputs and pricing, which is most of what is needed. It leaves a real ambiguity: the singular 'Team profile' framing conflicts with a limit parameter defaulting to 20, so it is unclear whether multiple teams can be returned, and nothing explains behavior when name is omitted entirely (0 required params).

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 coverage is 100%, so the schema already documents name, limit and league with examples and an enum-like hint. The description adds no per-parameter meaning beyond repeating that league appears in the output, so 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?

States the resource precisely ('Team profile from the Footalytics ratings table') and enumerates the returned fields: current rating, games tracked, league. That differentiates it from siblings like get_match_prediction and list_results, though the verb is only implied by the tool name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance and no mention of alternatives such as get_match_prediction or list_fixtures. The only implied routing is 'use this for team-level rating data', which the agent must infer from the field list.

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