Skip to main content
Glama
Sign In

TaScan

by io.github.snowbikemike
OverviewDiscussionsAdmin

tascan_update_worker

Idempotent

Update a worker profile (name, phone, email, actor_kind), or deactivate / reactivate the worker (active false / true with an optional reason: receipted as a ledger event first, never a delete; a merged record is never reactivated). Changing actor_kind to or from agent or admin is refused for every key: only an org owner or admin, signed in to the portal, can do that.

Input Schema

NameRequiredDescriptionDefault
nameNoNew name
emailNoNew email
phoneNoNew phone
activeNoSR-API3: false deactivates the worker, true reactivates it (receipted)
reasonNoWhy (recorded with an active change; at most 500 characters)
worker_idYesWorker ID
actor_kindNoWhat this worker row stands for (to or from agent / admin: owner or admin session only)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / active
      Added value: +{
+  "description": "SR-API3: false deactivates the worker, true reactivates it (receipted)",
+  "type": "boolean"
+}
    • addedInput schema / properties / reason
      Added value: +{
+  "description": "Why (recorded with an active change; at most 500 characters)",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / actor_kind
      Added value: +{
+  "description": "What this worker row stands for (to or from agent / admin: owner or admin session only)",
+  "enum": [
+    "person",
+    "agent",
+    "admin",
+    "device"
+  ],
+  "type": "string"
+}
  3. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Adds substantial behavior beyond annotations: active changes are receipted as a ledger event first, never a hard delete, merged records cannot be reactivated, and actor_kind changes to/from agent or admin are refused for every key except an owner/admin portal session. This gives rich side-effect, permission, and constraint context.

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?

Two sentences with no filler; the main action and fields are front-loaded. It is somewhat dense, with clustered parentheticals about receipting and reactivation, but every clause contributes operational information.

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?

Given 100% schema coverage and useful annotations, the description covers the key mutation semantics, permissions, and constraints. It does not describe the return value or response shape, and there is no output schema to fill that gap, but the core calling information is present.

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 description coverage is 100%, so the baseline is 3. The description adds meaning for active, reason, and actor_kind by explaining ledger receipting, optional reason semantics, reactivation restrictions for merged records, and the specific permission rule for agent/admin transitions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: update a worker profile and toggle active status. It distinguishes deactivation from deletion by saying 'never a delete', but does not explicitly name or differentiate from other worker-related siblings such as delete_worker or merge_workers.

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?

Provides clear context for when to use active false/true and the optional reason, and clarifies that deactivation is never a delete. It also states exclusions: merged records cannot be reactivated and actor_kind changes to or from agent/admin are refused. However, it does not direct the agent to alternatives like delete_worker for permanent removal.

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

All TaScan toolsInspect
Try in Browser
Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources