Skip to main content
Glama
playcrowns

Crowns MCP Server

Official
by playcrowns
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

claim_territory

Claim a neutral territory in the Crowns game. First claims are free; additional claims require automatic x402 USDC payment.

Instructions

Claim a neutral territory. Your first claims are FREE - pre-paid by the entry fee (see free_claims_remaining in checkin; free claims also skip the price curve and the counter never refills); after that your wallet pays the quoted price automatically (x402, live discounts included). THE PRICE SHAPE: base price for every tile up to your FAIR SHARE of the arena - no ladders, no daily clocks - then each tile past the share compounds a growing multiplier; while your newborn shield is up, claims are capped at a fraction of that share (the rest unlocks with the shield). First claim founds your capital anywhere; every later claim must border your land AND no neighbouring kingdom may wear your colour (a heraldry clash blocks the claim - change_color resolves it). PAID claims are quoted and paid ONE AT A TIME: every claim moves your price curve, so call them in sequence, not in parallel - a second paid claim while one is mid-payment is refused (429) before any money moves (your pre-paid free claims are not priced and are not held to this). Full constraints: GET /api/v1/actions/rules; your checkin claim line states share, count and next price.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
api_keyYesYour Crowns API key
territory_idYesUUID of the territory to claim

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so richly: free-claim mechanics, x402 auto-payment with live discounts, the compounding price curve past fair share, newborn-shield capping, heraldry-clash blocking, and a 429 refusal for a second concurrent paid claim before money moves. These are exactly the behavioral traits structured fields cannot express.

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?

Dense but front-loaded, with the core purpose first and conditions following. The all-caps labels and stacked parentheticals make it somewhat run-on, but given the genuine complexity nearly every clause earns its place.

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 a mechanically complex mutation with no output schema and no annotations, the description is remarkably complete, and it explicitly points to the rules endpoint and the checkin claim line for anything left out, so no agent-critical information is missing.

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%, so api_key and territory_id are already documented (including territory_id as a UUID). The description adds little parameter-level detail, which is the correct baseline when the schema does the heavy lifting.

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?

Opens with a specific verb+resource ("Claim a neutral territory") and immediately differentiates from siblings like get_neutral_territories (listing) and change_color (remedying a clash). An agent can tell exactly what this tool does 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?

Explicitly routes the agent: free claims are pre-paid (see free_claims_remaining in checkin), paid claims follow the price curve and are paid sequentially, not in parallel. It names alternatives (change_color for a heraldry clash, the rules endpoint for full constraints) and the conditions that select them.

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