Skip to main content
Glama
Sign In
tarkov-mcp

tarkov-mcp

by glennpai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List hideout stations

list_hideout_stations

List all hideout stations with their max level in Escape from Tarkov. Supports multiple languages and game modes.

Instructions

List all hideout stations (e.g. Workbench, Medstation, Library) with their max level.

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": "list_hideout_stations"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage for names/descriptions. Defaults to "en".
gameModeNoGame mode to query. Defaults to the server's configured game mode ("regular").

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations exist, so the description carries the behavioral burden. It does disclose the read-only listing behavior and the included max-level field, but it does not mention ordering, pagination, or how lang/gameMode affect results. For a simple list tool, this is acceptable but not richly transparent.

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?

The description is a single front-loaded sentence with no filler. The parenthetical examples clarify the resource type without adding bulk, and the key return field is included.

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?

For a low-complexity tool with two fully documented optional parameters and no output schema, the description covers the essential missing context: scope and the included max-level field. It is sufficient, though ordering or response-shape details could have added extra completeness.

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 100%, and both lang and gameMode already have meaningful enum-based descriptions with defaults. The tool description adds no parameter-level meaning, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('List'), names the resource ('hideout stations'), and clarifies scope with 'all' and representative examples. It also states the key returned attribute (max level), making the purpose unambiguous and distinguishing it from the singular get_hideout_station.

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?

The description implies collection-level usage by saying 'List all', which contrasts with the singular sibling get_hideout_station. However, it does not explicitly state when to use this tool versus the sibling or provide any exclusion criteria.

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

Deploy Server

Other Tools