Skip to main content
Glama

Get Team Salaries

get_team_salaries
Read-only

Retrieves weekly player and staff salaries for a specified team ID, helping you track payroll costs and manage your team's finances.

Instructions

Weekly player and staff salaries of your own team.

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>"
    },
    "name": "get_team_salaries"
  }
}

Input Schema

NameRequiredDescriptionDefault
team_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds two useful behavioral facts — that values are weekly and that they cover staff as well as players — but discloses nothing about limits, whether historical weeks are included, or how the response is shaped.

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 short sentence with no filler, and the key qualifier ('weekly') is front-loaded. It is terse to the point of omitting needed detail, but nothing written is wasted.

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?

An output schema exists, so return format needn't be explained, and the read-only nature is covered by annotations. However, for a tool requiring a team_id with zero schema documentation, the description should clarify what that id refers to and whether it is constrained to the caller's own team.

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% and the single parameter team_id is undocumented anywhere. The description's phrase 'your own team' arguably conflicts with requiring a team_id, leaving the agent unsure whether the id must match its own team or may be any team.

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 resource (player and staff salaries) with a time granularity (weekly) and a scope (own team), which is enough to tell it apart from siblings like get_team_economy or get_team_staff. It lacks an explicit verb, but the noun phrase is specific enough for an agent to know what it retrieves.

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?

There is no when-to-use guidance, no prerequisites, and no mention of an alternative tool for related financial data such as get_team_economy. The phrase 'your own team' implies a scope restriction but never states what that means for the caller or when this is preferable to other team-info tools.

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