EasyTerritory MCP

Delete Point Layer

delete_point_layer

Destructive

Point-layer delete: removes one point layer and its account points from the Territory Solution and the open map, in one synchronous call. Needs point_layer (the layer id or its exact unique label), plus map_session_id or ts_handle. Territories, part overlays, and other point layers stay. A layer that is already gone returns ok with already_absent=true; an ambiguous label returns AMBIGUOUS_POINT_LAYER with matching_point_layers. ingest_accounts does not replace an existing layer; delete it here first. A visit layer derived from the deleted layer is reported and kept.

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": {
      "point_layer": "<point_layer>"
    },
    "name": "delete_point_layer"
  }
}

Input Schema

Name	Required	Description
`ts_handle`	No	Territory Solution reference (tsh_...) from a build, ingest_accounts, import_geojson, import_designer_project, or get_map_visualization; Territory Solutions are not accepted inline.
`point_layer`	Yes	Point layer to delete: the point_layer id, or an exact unique layer label.
`map_session_id`	No	Open map session (msess_...) from get_map_visualization. Its Territory Solution is the input; omit ts_handle when set.

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.

Changed7 schema fields changedNov 1, 2026

addedInput schema / properties / map_session_id / description

Added value: +"Open map session (msess_...) from get_map_visualization. Its Territory Solution is the input; omit ts_handle when set."

addedInput schema / properties / point_layer / description

Added value: +"Point layer to delete: the point_layer id, or an exact unique layer label."

addedInput schema / properties / ts_handle / description

Added value: +"Territory Solution reference (tsh_...) from a build, ingest_accounts, import_geojson, import_designer_project, or get_map_visualization; Territory Solutions are not accepted inline."

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"
+      },
+      "already_absent": {
+        "type": "boolean"
+      },
+      "deleted_point_layer": {
+        "type": [
+          "null",
+          "string"
+        ]
+      },
+      "derived_point_layers_kept": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "do_this_next": {
+        "type": "string"
+      },
+      "map_refresh": {
+        "type": "object"
+      },
+      "remaining_point_layers": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "removed_feature_count": {
+        "type": "integer"
+      },
+      "requested_point_layer": {
+        "type": "string"
+      },
+      "routes_still_referencing": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "ts_handle": {
+        "type": "string"
+      }
+    },
+    "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: -"delete_point_layerDictOutput"

AddedOct 12, 2026

TDQS

A4.9/5.0

Behavior5/5

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

The annotations already mark this as destructive and non-readonly, and the description adds substantial behavioral detail beyond them: the call is synchronous, account points are removed, other layers stay, already-absent layers return ok with already_absent=true, and ambiguous labels return AMBIGUOUS_POINT_LAYER with matching_point_layers. It also notes that a derived visit layer is reported and kept.

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 description is front-loaded with the core delete action and scope, then adds error and edge-case behavior. Every sentence carries relevant operational information without filler.

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?

Given the destructive annotations, complete schema coverage, and an output schema, the description is complete enough for an agent to invoke the tool correctly. It covers prerequisites, scope boundaries, error outcomes, and the interaction with ingest_accounts.

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%, so the schema already defines the parameters. The description adds useful relationship semantics by stating that point_layer is required and that map_session_id or ts_handle is needed, plus clarifying that point_layer may be an id or exact unique label.

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 action and resource: 'removes one point layer and its account points from the Territory Solution and the open map.' It also clarifies scope by saying territories, part overlays, and other point layers remain, which distinguishes this from broader deletion tools.

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?

It explicitly names the sibling relationship with ingest_accounts, explaining that ingest_accounts does not replace an existing layer and that the layer must be deleted here first. It also specifies the required inputs and the ts_handle/map_session_id alternative, giving clear operational context.

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?