Skip to main content
Glama
Sign In

EasyTerritory MCP

by ai.easyterritory
OverviewDiscussionsAdmin

Get Part Selection

get_part_selection
Read-onlyIdempotent

Returns the state of a map selection task (selection_task_id from request_part_selection, or active_selection_task_id in ezt://map-sessions/{id}/state): status awaiting_user_selection, committed, expired, or cancelled, and once committed the selected part_ids (with assigned and unassigned part_ids when a TAL is active). While awaiting, the response carries recommended_poll_delay_ms. Committed part_ids feed realign, create_territory_from_parts, or analyze.

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": {
      "selection_task_id": "<selection_task_id>"
    },
    "name": "get_part_selection"
  }
}

Input Schema

NameRequiredDescriptionDefault
selection_task_idYesselection_task_id (psel_...) from request_part_selection.

Output Schema

NameRequiredDescriptionDefault
okYes
errorNoPresent when ok is false.
resultNoPresent when ok is true.
warningsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / selection_task_id / description
      Added value: +"selection_task_id (psel_...) from request_part_selection."
    • removedOutput schema / additionalProperties
      Removed value: -true
    • addedOutput schema / properties
      Added value: +{
+  "error": {
+    "description": "Present when ok is false.",
+    "properties": {
+      "ask_user": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "code": {
+        "type": "string"
+      },
+      "details": {
+        "type": "object"
+      },
+      "do_this_next": {
+        "type": "object"
+      },
+      "message": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "ok": {
+    "type": "boolean"
+  },
+  "result": {
+    "description": "Present when ok is true.",
+    "properties": {
+      "active_tal_id": {
+        "type": "string"
+      },
+      "committed_at": {
+        "type": "string"
+      },
+      "created_at": {
+        "type": "string"
+      },
+      "do_this_next": {
+        "type": "object"
+      },
+      "expires_at": {
+        "type": "string"
+      },
+      "map_session_id": {
+        "type": "string"
+      },
+      "part_layer": {
+        "type": "string"
+      },
+      "poll_interval_ms": {
+        "type": "integer"
+      },
+      "poll_loop": {
+        "type": "object"
+      },
+      "prompt": {
+        "type": "string"
+      },
+      "purpose": {
+        "type": "string"
+      },
+      "recommended_poll_delay_ms": {
+        "type": "integer"
+      },
+      "selection": {
+        "type": "object"
+      },
+      "selection_task_id": {
+        "type": "string"
+      },
+      "status": {
+        "type": "string"
+      },
+      "ts_identity": {
+        "type": "object"
+      }
+    },
+    "type": "object"
+  },
+  "warnings": {
+    "items": {
+      "properties": {
+        "code": {
+          "type": "string"
+        },
+        "message": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "type": "array"
+  }
+}
    • addedOutput schema / required
      Added value: +[
+  "ok"
+]
    • removedOutput schema / title
      Removed value: -"get_part_selectionDictOutput"
  2. Changed1 schema field changed
    • removedInput schema / properties / guidance_handle
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Guidance Handle"
-}
  3. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already establish that this is a safe read-only, idempotent operation. The description adds substantive behavioral detail beyond that: it lists all possible task statuses, explains recommended_poll_delay_ms while awaiting, describes conditional assigned/unassigned part_ids when a TAL is active, and identifies downstream consumers.

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 definition is compact and front-loaded with the return-state purpose. Every clause carries actionable information: status values, polling delay, conditional TAL output, and downstream usage.

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?

Although an output schema exists, the description still provides enough operational context for correct invocation and follow-up. It covers task origins, statuses, polling behavior, and how committed part_ids are used.

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 coverage is 100%, and the schema already documents that selection_task_id comes from request_part_selection. The description adds useful meaning by noting the alternate source, active_selection_task_id in ezt://map-sessions/{id}/state.

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 states a specific verb and resource: it returns the state of a map selection task, and it enumerates the possible statuses. It also distinguishes the tool from the sibling request tool by naming request_part_selection as the source of the task ID.

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

Usage Guidelines4/5

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

The description makes the usage context clear: call it with a selection_task_id from request_part_selection or the active task ID in map-session state. It explains polling while awaiting and downstream use once committed, but it does not explicitly name when not to use it versus alternatives such as get_map_selection.

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

All EasyTerritory MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources