Skip to main content
Glama

Get Team Facilities

get_team_facilities
Read-only

Retrieve your team's building facilities, including current levels, maximum level, and weekly upkeep costs. Use it to plan upgrades and budget maintenance.

Instructions

Building available for your own team: levels, max level and weekly upkeep.

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

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.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 added value is limited to enumerating the returned fields (levels, max level, upkeep). It says nothing about permission scope, whether other teams can be queried, or cost calculation semantics behind 'weekly upkeep'.

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?

One compact sentence with the object of the call front-loaded and the returned fields listed afterward. Nothing is wasted, though it could be tightened by replacing the vague 'Building available' opening.

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?

An output schema exists, so return-value details need not be repeated; the description still previews the key fields. For a single-parameter read tool this covers the essentials, with the main remaining gap being the scope of 'your own team' versus the required team_id.

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 description coverage is 0% for the single team_id parameter, but the phrase 'your own team' partially disambiguates what the ID should reference. It does not state format, whether arbitrary team IDs are accepted, or what happens on an invalid ID.

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 the resource (team facilities/buildings) and the data returned: levels, max level and weekly upkeep. It is clear enough to distinguish from roster/economy siblings, though it never states a verb and 'Building available' is slightly ambiguous phrasing.

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 and no mention of related tools such as get_team_arena or get_team_economy, which an agent would plausibly confuse with facility data. The only implied context is 'for your own team', which is not framed as a rule.

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