Skip to main content
Glama

station

Read-onlyIdempotent

Administer one of your faction's stations or outposts: rename, access control, and build policy (Must be docked at a station or outpost your faction owns. Action 'info' (any member) shows the current configuration; all other actions need the ManageBases permission. Outposts support only 'info', 'set_name', and 'set_description' (they have no services and are members-only by design); the remaining actions are station-only. Actions: set_name (name), set_description (description, max 500 chars), set_public (public: true/false — when false only the owning faction, allowed factions, and allowed players may dock), set_build_policy (allow_outsiders: true/false — whether non-members may build their own facilities here; those tenants pay rent each cycle to your faction treasury), set_service_access (service=market|refuel|repair|shipyard|crafting|salvage_yard|missions + access=public|allies|faction — gate an individual service to the owning faction and optionally allies), set_market_fee (fee_percent 0-10 — listing fee outside traders pay, to your treasury), set_refuel_price (price per fuel unit) and set_repair_price (price per hull point — outside-pilot charges that flow to your treasury), set_auto_buy_fuel (auto_buy_fuel: true/false — off by default; when on, any docked pilot can sell fuel from their ship's tank into your shared tank at live scarcity-based prices, paid from your faction's treasury, capped to what it can afford), allow_player/remove_player/ban/unban (player: id or username), allow_faction/remove_faction (faction: id). Banning a player also drops them from the allow list and immediately blocks docking. set_contraband (contraband_items: array of item IDs) replaces the station market contraband list. An empty array allows all items. reset_contraband restores the default rules. Both actions require a player-owned station or mobile base. Smuggling skill bypass still applies. Empire customs remain unchanged. Existing market orders remain active after a policy change; new and modified orders follow the current policy.)

Input Schema

NameRequiredDescriptionDefault
nameNoNew station name (set_name)
priceNoPrice for set_refuel_price (per unit) or set_repair_price (per hull point)
accessNoAccess level for set_service_access
actionYesWhat to configure on your faction's station
playerNoTarget player id or username (allow_player/remove_player/ban/unban)
publicNoWhether anyone may dock (set_public)
factionNoTarget faction id (allow_faction/remove_faction)
serviceNoService type for set_service_access (market, refuel, repair, shipyard, crafting, salvage_yard, missions)
session_idYesYour session ID from login/register
descriptionNoNew station description (set_description)
fee_percentNoMarket listing fee percent 0-10 (set_market_fee)
auto_buy_fuelNoWhether the station automatically buys fuel from docked pilots at live scarcity-based prices, paid from your faction's treasury capped to affordability (set_auto_buy_fuel; off by default)
allow_outsidersNoWhether non-members may build facilities here (set_build_policy)
contraband_itemsNoReplacement contraband item IDs for this player-owned station or mobile base (set_contraband). Required for set_contraband; [] allows all items. reset_contraband restores defaults. Smuggling skill bypass still applies; empire customs remain unchanged.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "info",
      -  "set_name",
      -  "set_description",
      -  "set_public",
      -  "set_build_policy",
      -  "set_service_access",
      -  "set_market_fee",
      -  "set_refuel_price",
      -  "set_repair_price",
      -  "set_auto_buy_fuel",
      -  "allow_player",
      -  "remove_player",
      -  "ban",
      -  "unban",
      -  "allow_faction",
      -  "remove_faction"
      -]New value: +[
      +  "info",
      +  "set_name",
      +  "set_description",
      +  "set_public",
      +  "set_build_policy",
      +  "set_service_access",
      +  "set_market_fee",
      +  "set_refuel_price",
      +  "set_repair_price",
      +  "set_auto_buy_fuel",
      +  "set_contraband",
      +  "reset_contraband",
      +  "allow_player",
      +  "remove_player",
      +  "ban",
      +  "unban",
      +  "allow_faction",
      +  "remove_faction"
      +]
    • addedInput schema / properties / contraband_items
      Added value: +{
      +  "description": "Replacement contraband item IDs for this player-owned station or mobile base (set_contraband). Required for set_contraband; [] allows all items. reset_contraband restores defaults. Smuggling skill bypass still applies; empire customs remain unchanged.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  2. Added
  3. Removed
  4. Added

TDQS

A3.9/5.0
Behavior1/5

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

The description is rich in behavior (docking blocks on ban, contraband empty-array semantics, treasury-funded auto-buy), but it directly contradicts the annotations: every described action (set_name, ban, set_build_policy) is a mutation while readOnlyHint=true and idempotentHint=true are declared. The structured safety profile is wrong for this tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well front-loaded with purpose and preconditions, and every sentence carries real information, but the bulk is a single dense paragraph enumerating 18 actions, which is hard to scan. It is information-rich yet structurally a wall of text rather than a navigable list.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 18-action, 14-parameter tool with no output schema, the description covers preconditions, permission model, per-action semantics, outpost limitations, and side effects thoroughly. An agent has essentially everything needed to select and invoke the right action.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3, but the description goes further by explaining what each action does with its parameters (e.g. set_public semantics when false, allow_outsiders meaning tenants pay rent, fee_percent 0-10 as an outside-trader listing fee, price dual-use for refuel/repair). It adds operational meaning beyond field labels.

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?

States a specific verb and resource ('Administer one of your faction's stations or outposts') followed by the domains it covers (rename, access control, build policy). An agent can immediately distinguish this from siblings like build_outpost, dismantle_outpost, or build_base without opening the schema.

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

Usage Guidelines5/5

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

Explicit preconditions ('Must be docked at a station or outpost your faction owns'), permission routing ('info' any member; all other actions need ManageBases), and hard exclusions (outposts support only info/set_name/set_description; remaining actions are station-only). This is textbook when/when-not guidance.

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