Skip to main content
Glama
Sign In

TaScan

by io.github.snowbikemike
OverviewDiscussionsAdmin

tascan_update_event

Idempotent

Update an event / task list (name, description, team_mode, multi_instance, timer_mode). team_mode and multi_instance cannot both be true.

Input Schema

NameRequiredDescriptionDefault
nameNoNew name
list_idYesTask list (event) ID
team_modeNoTeam mode — shared completions
timer_modeNoTimer mode (auto or manual)
descriptionNoNew description
access_levelNoSR-S2: raise freely; lowering needs an owner/admin-tier key (tascan_set_access rules)
agent_assigneeNoSR-S2: the agent_id whose key alone may reach this list, or null (removing one needs an owner/admin-tier key)
multi_instanceNoMulti-instance — each worker gets isolated copy
assigned_worker_idsNoWorker UUIDs to assign to this event (additive — workers not named are left alone). Each gets a personal tap-to-open link. Note: a worker holds one event assignment per project — assigning moves them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / access_level
      Added value: +{
+  "description": "SR-S2: raise freely; lowering needs an owner/admin-tier key (tascan_set_access rules)",
+  "enum": [
+    "open",
+    "assigned",
+    "secured",
+    null
+  ],
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedInput schema / properties / agent_assignee
      Added value: +{
+  "description": "SR-S2: the agent_id whose key alone may reach this list, or null (removing one needs an owner/admin-tier key)",
+  "type": [
+    "string",
+    "null"
+  ]
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / assigned_worker_ids
      Added value: +{
+  "description": "Worker UUIDs to assign to this event (additive — workers not named are left alone). Each gets a personal tap-to-open link. Note: a worker holds one event assignment per project — assigning moves them.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
  3. Changed4 schema fields changed
    • addedInput schema / properties / multi_instance
      Added value: +{
+  "description": "Multi-instance — each worker gets isolated copy",
+  "type": "boolean"
+}
    • changedInput schema / properties / team_mode / description
      Previous value: -"Team mode"New value: +"Team mode — shared completions"
    • changedInput schema / properties / timer_mode / description
      Previous value: -"Timer mode"New value: +"Timer mode (auto or manual)"
    • changedInput schema / properties / timer_mode / type
      Previous value: -"boolean"New value: +"string"
  4. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true, destructiveHint=false and non-read-only, so the safety profile is covered. The description adds the mutual-exclusion rule, which is useful, but says nothing about partial-update semantics (whether omitted fields are left untouched) or permission requirements for sensitive fields like access_level.

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?

Two short, front-loaded sentences with zero filler; the field list gives an at-a-glance scope and the constraint sentence adds real information rather than restating the name.

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

Completeness3/5

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

For a 9-parameter mutation with no output schema, the description covers scope and one constraint, and the rich schema covers per-field meaning. It still leaves the agent guessing about partial-update behavior and what the call returns, which matters for an update tool.

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

Parameters3/5

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

Schema description coverage is 100% and every parameter carries meaningful notes (including the SR-S2 access rules and the additive nature of assigned_worker_ids), so the schema does the heavy lifting. The description only echoes five parameter names without adding semantics beyond them.

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 (Update) and resource (event / task list), and enumerates the mutable fields. The 'event / task list' phrasing implicitly separates it from tascan_update_task and tascan_update_project, but no sibling is named outright.

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 sentence 'team_mode and multi_instance cannot both be true' is a genuine usage constraint, but there is no guidance on when to choose this over tascan_update_task, tascan_set_access, or tascan_update_project, and no stated prerequisites.

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