TaScan

tascan_update_zone

Idempotent

Update a geofenced zone — move the center, resize the radius, change the routing target, toggle zone-lock, or deactivate it (is_active=false).

Input Schema

TableJSON Schema

Name	Required	Description
`lat`	No
`lng`	No
`kind`	No
`name`	No
`polygon`	No	Replace geometry with a polygon ([[lat,lng],...], ≥3 vertices); pass null to revert to a circle
`zone_id`	Yes	Zone ID
`radius_m`	No
`is_active`	No
`notify_email`	No
`required_ppe`	No
`task_list_id`	No
`auto_clock_in`	No	Writes a shift_start when the WORKER PAGE, while open, sees the phone enter the zone; detection is pull-based, there is no background geofencing. For a background-free presence event use a gate NFC/QR scan.
`enter_message`	No
`auto_clock_out`	No	Writes a shift_end when the WORKER PAGE, while open, sees the phone leave the zone; detection is pull-based, there is no background geofencing. For a background-free presence event use a gate NFC/QR scan.
`notify_on_exit`	No
`alert_on_breach`	No
`enforce_on_list`	No
`notify_on_enter`	No
`ppe_photo_required`	No
`sms_worker_on_exit`	No
`task_list_on_enter`	No
`sms_worker_on_enter`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 20, 2026

addedInput schema / properties / auto_clock_in / description

Added value: +"Writes a shift_start when the WORKER PAGE, while open, sees the phone enter the zone; detection is pull-based, there is no background geofencing.  For a background-free presence event use a gate NFC/QR scan."

addedInput schema / properties / auto_clock_out / description

Added value: +"Writes a shift_end when the WORKER PAGE, while open, sees the phone leave the zone; detection is pull-based, there is no background geofencing.  For a background-free presence event use a gate NFC/QR scan."

Changed8 schema fields changedSep 3, 2026

addedInput schema / properties / alert_on_breach
```
Added value: +{
+  "type": "boolean"
+}
```
addedInput schema / properties / enter_message
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / kind

Added value: +{
+  "enum": [
+    "work_site",
+    "hazard",
+    "containment",
+    "restricted"
+  ],
+  "type": "string"
+}

addedInput schema / properties / ppe_photo_required
```
Added value: +{
+  "type": "boolean"
+}
```

addedInput schema / properties / required_ppe

Added value: +{
+  "items": {
+    "enum": [
+      "hard_hat",
+      "safety_glasses",
+      "hi_vis_vest",
+      "gloves",
+      "steel_toe_boots",
+      "hearing_protection",
+      "harness",
+      "respirator",
+      "face_shield"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / sms_worker_on_enter
```
Added value: +{
+  "type": "boolean"
+}
```
addedInput schema / properties / sms_worker_on_exit
```
Added value: +{
+  "type": "boolean"
+}
```
addedInput schema / properties / task_list_on_enter
```
Added value: +{
+  "type": "string"
+}
```

Changed6 schema fields changedAug 26, 2026

addedInput schema / properties / auto_clock_in
```
Added value: +{
+  "type": "boolean"
+}
```
addedInput schema / properties / auto_clock_out
```
Added value: +{
+  "type": "boolean"
+}
```
addedInput schema / properties / notify_email
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / notify_on_enter
```
Added value: +{
+  "type": "boolean"
+}
```
addedInput schema / properties / notify_on_exit
```
Added value: +{
+  "type": "boolean"
+}
```

addedInput schema / properties / polygon

Added value: +{
+  "description": "Replace geometry with a polygon ([[lat,lng],...], ≥3 vertices); pass null to revert to a circle",
+  "items": {
+    "items": {
+      "type": "number"
+    },
+    "type": "array"
+  },
+  "type": "array"
+}

AddedAug 18, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true, so the safety profile is covered. The description adds specific behaviors like 'deactivate it (is_active=false)' and the ability to revert polygon to a circle, which go beyond the annotations. However, it does not disclose side effects beyond the listed updates, such as notification implications or validation behavior. Given the annotations, the added context is adequate but not rich.

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 a single, tightly written sentence that front-loads the primary purpose and lists the key update capabilities. There is no redundancy or filler; every phrase contributes to understanding the tool's scope.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 22 parameters, many lacking schema descriptions, and no output schema, the description is insufficient for an agent to confidently use the tool correctly. It omits critical context for the majority of parameters (e.g., enforcement options, notifications, task list assignments) and does not describe the expected return value or side effects. The description provides only a high-level overview, leaving significant gaps for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 18%, so the description carries the burden of explaining parameters. It mentions a few (center, radius, routing target, zone-lock, is_active) but does not systematically cover the remaining 20+ parameters like notify_email, required_ppe, enter_message, or auto_clock_in. The schema descriptions for auto_clock_in/out add context, but most parameters remain unexplained in both schema and description, leaving agents to guess their meaning from names alone.

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 ('update') and resource ('geofenced zone'), and enumerates the concrete operations it supports (move center, resize radius, change routing target, toggle zone-lock, deactivate). It clearly differentiates from create_zone and other update tools via the resource type and action list.

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

Usage Guidelines3/5

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

The description implies usage for modifying an existing zone, but it does not explicitly state when to use this over alternatives (e.g., tascan_create_zone) or mention any prerequisites such as requiring an existing zone_id. The context is inferable from the tool name and sibling list, but there is no explicit guidance or exclusion of non-update scenarios.

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

All TaScan 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.

tascan_update_zone

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources