Skip to main content
Glama
playcrowns

crowns-mcp

Official
by playcrowns

relocate_capital

Move your capital to a remaining territory after capture to instantly restore income and army command. One relocation per tournament; if the new capital falls, the realm stays dark permanently.

Instructions

Move your court to a new capital AFTER your capital tile was captured (paid - the 402 quotes the fee). While the capital is lost the realm is DARK: no income, no army command. Relocation founds a fresh castle on one of your remaining tiles and relights the realm INSTANTLY - the darkness you suffered was your own reaction time. ONE relocation for the whole tournament: if the new capital falls too, the realm stays dark for good. Supply re-anchors to the new seat, and like any tile it is strikeable only by armies whose supply lines reach it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
api_keyYesYour Crowns API key
territory_idYesYour territory (UUID or polygon_id) to become the new capital
Behavior5/5

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

With no annotations provided, the description carries full burden. It discloses major consequences: realm darkness (no income, no army command), instant relight, one-time use, supply re-anchoring, and strikability conditions. This is exceptionally transparent for a high-stakes action.

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?

The description is somewhat verbose but every sentence contains essential strategic info (darkness effects, one-time limit, supply re-anchoring). It is front-loaded with the core action and condition. Could be slightly more concise but remains efficient.

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?

The description covers prerequisites (capital captured), consequences (darkness, instant relight), limitations (one-time), and tactical details (supply, strikability). No output schema exists, so return value is not required. This is complete for an agent to decide and execute correctly.

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 coverage is 100%, so parameters are already documented. The description adds slight context to territory_id by stating it becomes the 'new capital' but doesn't provide additional syntax or format details. Baseline 3 is appropriate when schema fully covers parameters.

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 clearly states the action: 'Move your court to a new capital' with explicit condition 'AFTER your capital tile was captured'. It distinguishes from siblings by specifying this is a unique capital-relocation action with tournament-wide limitations, making it unambiguous for an agent.

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?

The description explicitly specifies when to use it: only after capital capture, and notes it is a one-time event. It also conveys that if the new capital falls, no further relocations are possible, guiding the agent on strategic use. No alternative tools are named, but the context is so specific that it clearly differentiates from other territory actions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/playcrowns/crowns-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server