EasyTerritory MCP

Load Analysis Panel

load_analysis_panel

Shows a completed analyze result in the open map's analysis dock (single or compare). Needs map_session_id and the analyze task_id/job_id or the full analyze result (with tal_analyses and ts_identity; a partial object returns INVALID_REQUEST). presentation_mode: single, compare, executive, or diagnostic. dismiss=true hides the dock and keeps the statistics on the session. Changes nothing in the Territory Solution. analyze with analysis_panel=single fills the dock in the same call.

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": {
      "map_session_id": "<map_session_id>"
    },
    "name": "load_analysis_panel"
  }
}

Input Schema

Name	Required	Description
`roles`	No
`job_id`	No	Compatibility alias for task_id.
`labels`	No
`dismiss`	No	true hides the whole dock, header bar included, and keeps stored stats. It takes no analyses, task_id, labels, roles, or presentation_mode.
`task_id`	No	Completed analyze task_id. Same string as job_id. Hydrates analyses when analyses is omitted.
`analyses`	No
`map_session_id`	Yes	Open map session (msess_...) from get_map_visualization.
`presentation_mode`	No	Panel mode. territory_metric_grid is default_presentation.view inside the Analyze result, not a presentation_mode.

Output Schema

Name	Required	Description
`ok`	Yes
`error`	No	Present when ok is false.
`result`	No	Present when ok is true.
`warnings`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedNov 1, 2026

changedInput schema / properties / analyses / anyOf

Previous value: -[
-  {
-    "items": {
-      "additionalProperties": true,
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "additionalProperties": true,
+      "description": "A full Analyze result. Must include tal_analyses plus ts_identity, and territory_metric_grids when metrics exist. A thin {tal_analyses} object is rejected.",
+      "properties": {
+        "default_presentation": {
+          "type": "object"
+        },
+        "presentation_guidance_uri": {
+          "type": "string"
+        },
+        "tal_analyses": {
+          "type": "array"
+        },
+        "territory_metric_grids": {
+          "type": "array"
+        },
+        "ts_identity": {
+          "type": "object"
+        }
+      },
+      "required": [
+        "tal_analyses"
+      ],
+      "type": "object"
+    },
+    "maxItems": 4,
+    "minItems": 1,
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / analyses / title
```
Removed value: -"Analyses"
```

addedInput schema / properties / dismiss / description

Added value: +"true hides the whole dock, header bar included, and keeps stored stats. It takes no analyses, task_id, labels, roles, or presentation_mode."

addedInput schema / properties / job_id / description
```
Added value: +"Compatibility alias for task_id."
```

addedInput schema / properties / map_session_id / description

Added value: +"Open map session (msess_...) from get_map_visualization."

addedInput schema / properties / presentation_mode / description

Added value: +"Panel mode. territory_metric_grid is default_presentation.view inside the Analyze result, not a presentation_mode."

addedInput schema / properties / task_id / description

Added value: +"Completed analyze task_id. Same string as job_id. Hydrates analyses when analyses is omitted."

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": {
+      "analysis_count": {
+        "type": "integer"
+      },
+      "analysis_panel": {
+        "type": "object"
+      },
+      "dismissed": {
+        "type": "boolean"
+      },
+      "labels": {
+        "type": "array"
+      },
+      "map_session_id": {
+        "type": "string"
+      },
+      "presentation_mode": {
+        "type": "string"
+      },
+      "roles": {
+        "type": "array"
+      }
+    },
+    "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: -"load_analysis_panelDictOutput"

Changed1 schema field changedOct 9, 2026

removedInput schema / properties / guidance_handle

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Guidance Handle"
-}

First observedSep 29, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations declare non-read-only, non-destructive, non-idempotent, and the description adds real behavior: a partial object returns INVALID_REQUEST, dismiss hides the dock but keeps stored stats, and 'Changes nothing in the Territory Solution' scopes the side effect to session UI state. It doesn't mention any precondition that the map must be open/bound beyond 'open map'.

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?

Front-loads the core action and packs requirements, modes, and the dismiss edge case into tight sentences with no filler. Some sentences are telegraphic and would read better with light connective structure, but nothing is wasted.

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 an 8-param tool with annotations and an output schema, the description covers inputs, error behavior, side effects, and a sibling interaction. The only gap is the purpose of roles/labels, which the schema also leaves bare.

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?

Adds meaning beyond the 63%-covered schema: explains task_id/job_id are the same string, that dismiss=true takes no other arguments, enumerates presentation_mode values, and clarifies that territory_metric_grid is default_presentation.view rather than a mode. roles and labels remain unexplained in both schema and description.

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?

Names a specific verb and resource ('Shows a completed analyze result in the open map's analysis dock') and scopes it to single or compare panels. An agent can distinguish this from analyze/analyze_routes 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 Guidelines4/5

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

States the input requirement (map_session_id plus task_id/job_id or a full analyze result) and names an alternative path — 'analyze with analysis_panel=single fills the dock in the same call.' Missing an explicit when-not-to-use or a note on when dismiss should be preferred over re-loading.

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

All EasyTerritory MCP tools Inspect

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

Need Help?