Skip to main content
Glama

Get Team Economy

get_team_economy
Read-only

Fetch a team's economy recap with balance, available funds, expected sale proceeds, and transactions for financial review.

Instructions

Economy recap of your own team. Balance, available money, expected sale proceeds and transactions.

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

Input Schema

NameRequiredDescriptionDefault
sortNo
team_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, so the description's burden is lower. It adds a preview of the financial fields returned, but says nothing about permissions, whether the caller must own the team, or any freshness/caching behavior for the balance figures.

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 compact sentences with the resource stated first and the payload contents second. No filler, though the second sentence is a bare noun list without verbs, which is terse rather than informative.

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 values need no explanation, and the annotations carry the safety profile. However, the undocumented sort parameter and the unstated ownership requirement leave gaps an agent would need to resolve before calling correctly.

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 there are two parameters, one of which (sort, enum Asc/Desc, default null) is completely unaddressed by the description — an agent cannot tell what is being sorted or what the ordering applies to. team_id semantics are only obliquely implied by 'your own team', so the description does not compensate for the coverage gap.

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 ('economy recap of your own team') and enumerates the contents: balance, available money, expected sale proceeds, and transactions. It is clear what the tool returns, though it never explicitly distinguishes itself from the nearby get_team_salaries or get_team siblings.

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?

'Of your own team' implies a scope constraint, hinting the team_id should be the caller's team, but there is no explicit when-to-use statement and no routing to alternatives like get_team_salaries for wage detail. Usage is implied rather than stated.

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