Skip to main content
Glama
Sign In
sprinty

sprinty

by ebursztein
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

item_update

Update an existing sprint item by ID to change its metadata, gates/timeout, completed commit ID, or dependencies.

Instructions

Update an item by id: metadata, open-item gates/timeout, completed-item commit_id, and/or dependency ids.

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": {
      "id": "<id>"
    },
    "name": "item_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
noteNo
gatesNo
titleNo
commit_idNo
agent_tokenNo
descriptionNo
dependenciesNo
high_priorityNo
client_agent_idNo
gate_timeout_msNo
claim_generationNo
client_session_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.2.2
    • addedInput schema / properties / agent_token
      Added value: +{
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / claim_generation
      Added value: +{
+  "exclusiveMinimum": 0,
+  "type": "integer"
+}
    • addedInput schema / properties / client_agent_id
      Added value: +{
+  "maxLength": 200,
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / client_session_id
      Added value: +{
+  "maxLength": 200,
+  "minLength": 1,
+  "type": "string"
+}
  2. Changed3 schema fields changedv0.1.18
    • addedInput schema / properties / commit_id
      Added value: +{
+  "minLength": 7,
+  "type": "string"
+}
    • addedInput schema / properties / gate_timeout_ms
      Added value: +{
+  "anyOf": [
+    {
+      "exclusiveMinimum": 0,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
    • addedInput schema / properties / gates
      Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "category": {
+        "minLength": 1,
+        "type": "string"
+      },
+      "cwd": {
+        "minLength": 1,
+        "type": "string"
+      },
+      "kind": {
+        "enum": [
+          "test",
+          "typecheck",
+          "build",
+          "command",
+          "manual"
+        ],
+        "type": "string"
+      },
+      "spec": {
+        "minLength": 1,
+        "type": "string"
+      }
+    },
+    "required": [
+      "kind",
+      "spec"
+    ],
+    "type": "object"
+  },
+  "maxItems": 3,
+  "minItems": 1,
+  "type": "array"
+}
  3. Changed1 schema field changedv0.1.17
    • changedInput schema / properties / description / maxLength
      Previous value: -500New value: +800
  4. First observedv0.1.9

TDQS

A3.5/5.0
Behavior3/5

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

No annotations, so the description carries the full burden. It does disclose useful state-dependency (gates/timeout apply to open items, commit_id to completed items), but omits whether this requires an existing claim, what happens on a stale claim_generation, and whether unspecified fields are preserved or cleared.

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?

A single sentence, front-loaded with the verb and the id key, with zero filler. Every clause adds a distinct updatable surface 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 13-parameter mutation tool with no annotations and no output schema, the description covers the main conceptual axis (open vs completed items) but leaves authorization, concurrency control and partial-update semantics undocumented. It is adequate to guess the call shape but not to call it safely under contention.

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 0% across 13 parameters, so the description has to compensate and only partly does. It groups fields (metadata, gates, dependencies) and explains the conditional nature of gates/gate_timeout_ms and commit_id, but leaves agent_token, claim_generation, client_agent_id and client_session_id entirely unexplained, and 'metadata' is too vague to map to title/description/note/high_priority.

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 (item by id) and enumerates the updatable surfaces: metadata, gates/timeout, commit_id, dependencies. That enumeration distinguishes it from siblings like item_claim, item_progress and item_done, though it never names those siblings explicitly.

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?

Usage is only implied: the open-item/completed-item split hints at preconditions, but there is no explicit 'use this when…' or 'use item_done/item_claim instead for…' routing. An agent must infer that completing or claiming an item belongs to a different tool.

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

Deploy Server

Other Tools