Skip to main content
Glama

fenbs_update_item

Idempotent

Change a task by ref. Only the fields passed change. Moving between lanes needs permission to move tasks; changing the content needs permission to edit tasks. Keep the plan current as you learn: pass the whole plan, rewritten -- it replaces the old one, which is kept. Keep the remaining steps in steps and tick each one with doneSteps when it is done. Link or unlink related tasks with relatesTo and unrelate; the links already there are kept. When you finish, set testStatus and testNotes: how it was tested, and what was not. size is xs to xl (xl means split it). A task that ends without being delivered -- not to be fixed, a duplicate, cannot reproduce, obsolete -- gets that resolution with lane "done". Use resolution built (done, not live yet: pass it when the work still needs a deploy or release, and change it to shipped once it is live). Leaving resolution out when moving to done still defaults to shipped. archived true takes a Completed task off the board (it keeps its ref and history, and search still finds it); false puts it back. Only Completed tasks can be archived, and it needs permission to move tasks.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
refYes
fullNotrue: answer with the whole task. Otherwise the ref and what changed.
kindNo
laneNoThe lane, by its key. People see backlog as To Do, next as Next Up, doing as In Progress and done as Completed: use those names when you talk to people.
noteNoThe Problem box: what is wrong or missing, why it matters, and where -- file and line for code; repro steps for a bug. Written once; the fix goes in plan, not here.
planNoThe Plan box: how it will be done -- the approach, the files to change, the traps, and how it will be checked. The remaining steps go in steps, the checklist, not here. Leave it out until somebody knows; do not put a PLAN heading in the note instead. A replaced plan is kept: fenbs_get_item shows the earlier versions. Replaces the whole plan; "" clears it.
sizeNoHow big: xs (under an hour), s (an afternoon), m (a day or two), l (about a week), xl (too big -- split it). "none" takes a size off.
stepsNoRemaining steps: the ordered checklist of what is left to do, one short line each (at most 30, each under 300 characters), e.g. ["Write the SQL", "Build the API", "Ship"]. A string is a step not done yet; {text, done} sets done too. get_context shows each task in progress as "step n of N next: <text>", so the next assistant always sees what comes next. Tick them off with doneSteps as you go. Replaces the whole list; [] clears it. To tick one, pass doneSteps instead of the list.
titleNo
projectNoThe project this belongs to, by name -- for software, usually the repository or app. A new name creates the project; case is ignored when matching, so reuse the names fenbs_list_boards shows.
releaseNotrue: you are handing this In Progress task over and stopping work on it. Your claim is released, so the next window takes it without a "being worked by another session" warning. Only the session working the task can release it. Pass it in your final save before a /clear or a handover.
sessionNoA short name for this session or window, e.g. "Claude Code c--ws 33edc07d". Pass the same one on every call. Every window you open shares this connection, so without it fenbs shows only the connection name and cannot tell your windows apart.
archivedNotrue: archive this Completed task -- off the board, still in search and counts. false: put it back on the board. Only for a task in done (or passed with lane "done"). To tidy the whole Completed lane, use fenbs_archive_completed.
categoryNoAn optional second grouping, by name, e.g. "Checkout" or "Mobile". A new name creates it.
priorityNo1 is most urgent. 1-2 High, 3-5 Medium, 6-10 Low. Leave it out for 5, an ordinary task.
takeoverNoThe session you are taking over from, when it handed the task to you without releasing it (it crashed, or was cleared without a final save). If it names the session working the task, you take it over with no warning and the history notes the handover; if not, you get the usual warning.
unrelateNoRefs of linked tasks to unlink. Only these go; the other links stay.
doneStepsNoStep numbers to tick as done, 1 being the first (counted in the list after any steps you pass in the same call). The rest are left as they are.
relatesToNoRefs of tasks to link to this one, both ways. Added to the links it already has.
testNotesNoHow it was tested: what was checked, where (dev, a private API, live), the result -- and what was NOT checked. Rewritten whole, like plan; "" clears it.
resolutionNoHow a Completed task ended: shipped (the default when it moves to done), built (done, not live yet: pass it when the work still needs a deploy or release, and change it to shipped once it is live), wontfix, duplicate, cannotreproduce or obsolete. Only with lane "done", or on a task already done.
testStatusNoHow it was tested: untested (the default), tested, partly, failed, or needs-check -- what only a person can confirm (a store build, a real payment, a live page). Never claim tested for a check you did not run; use needs-check or partly and say what is left.
undoneStepsNoStep numbers to untick, back to not done.
linkDecisionsNoDecision refs (DEC-004) this task depends on. Added to those already linked.
whereItStandsNoWhere the work stands right now: done so far (commits), what is not done, anything still running, anything waiting on a person. Short; overwritten each time -- the old text is kept, and fenbs_get_item shows the earlier versions. The remaining steps live in steps, the checklist: tick them there instead of listing them here. Plan says how; steps say what is left; this says where things are. "" clears it. To save several tasks at once, use fenbs_save_progress.
unlinkDecisionsNoDecision refs to unlink from this task.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / doneSteps
      Added value: +{
      +  "description": "Step numbers to tick as done, 1 being the first (counted in the list after any steps you pass in the same call). The rest are left as they are.",
      +  "items": {
      +    "minimum": 1,
      +    "type": "integer"
      +  },
      +  "type": "array"
      +}
    • changedInput schema / properties / plan / description
      Previous value: -"The Plan box: how it will be done -- the steps, the files to change, the traps, and how it will be checked. Leave it out until somebody knows; do not put a PLAN heading in the note instead. Replaces the whole plan; \"\" clears it."New value: +"The Plan box: how it will be done -- the approach, the files to change, the traps, and how it will be checked. The remaining steps go in steps, the checklist, not here. Leave it out until somebody knows; do not put a PLAN heading in the note instead. A replaced plan is kept: fenbs_get_item shows the earlier versions. Replaces the whole plan; \"\" clears it."
    • addedInput schema / properties / release
      Added value: +{
      +  "description": "true: you are handing this In Progress task over and stopping work on it. Your claim is released, so the next window takes it without a \"being worked by another session\" warning. Only the session working the task can release it. Pass it in your final save before a /clear or a handover.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / steps
      Added value: +{
      +  "description": "Remaining steps: the ordered checklist of what is left to do, one short line each (at most 30, each under 300 characters), e.g. [\"Write the SQL\", \"Build the API\", \"Ship\"]. A string is a step not done yet; {text, done} sets done too. get_context shows each task in progress as \"step n of N next: <text>\", so the next assistant always sees what comes next. Tick them off with doneSteps as you go. Replaces the whole list; [] clears it. To tick one, pass doneSteps instead of the list.",
      +  "items": {
      +    "anyOf": [
      +      {
      +        "type": "string"
      +      },
      +      {
      +        "additionalProperties": false,
      +        "properties": {
      +          "done": {
      +            "type": "boolean"
      +          },
      +          "text": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "text"
      +        ],
      +        "type": "object"
      +      }
      +    ]
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / takeover
      Added value: +{
      +  "description": "The session you are taking over from, when it handed the task to you without releasing it (it crashed, or was cleared without a final save). If it names the session working the task, you take it over with no warning and the history notes the handover; if not, you get the usual warning.",
      +  "type": "string"
      +}
    • addedInput schema / properties / undoneSteps
      Added value: +{
      +  "description": "Step numbers to untick, back to not done.",
      +  "items": {
      +    "minimum": 1,
      +    "type": "integer"
      +  },
      +  "type": "array"
      +}
    • changedInput schema / properties / whereItStands / description
      Previous value: -"Where the work stands right now and what comes next: done so far (commits), not done, next step, anything still running, anything waiting on a person. Short; overwritten each time, the old text kept in History. Plan says how; this says where it is. \"\" clears it. To save several tasks at once, use fenbs_save_progress."New value: +"Where the work stands right now: done so far (commits), what is not done, anything still running, anything waiting on a person. Short; overwritten each time -- the old text is kept, and fenbs_get_item shows the earlier versions. The remaining steps live in steps, the checklist: tick them there instead of listing them here. Plan says how; steps say what is left; this says where things are. \"\" clears it. To save several tasks at once, use fenbs_save_progress."
  2. Changed3 schema fields changed
    • changedInput schema / properties / resolution / description
      Previous value: -"How a Completed task ended: shipped (the default when it moves to done), wontfix, duplicate, cannotreproduce or obsolete. Only with lane \"done\", or on a task already done."New value: +"How a Completed task ended: shipped (the default when it moves to done), built (done, not live yet: pass it when the work still needs a deploy or release, and change it to shipped once it is live), wontfix, duplicate, cannotreproduce or obsolete. Only with lane \"done\", or on a task already done."
    • changedInput schema / properties / resolution / enum
      Previous value: -[
      -  "shipped",
      -  "wontfix",
      -  "duplicate",
      -  "cannotreproduce",
      -  "obsolete"
      -]New value: +[
      +  "shipped",
      +  "built",
      +  "wontfix",
      +  "duplicate",
      +  "cannotreproduce",
      +  "obsolete"
      +]
    • addedInput schema / properties / session
      Added value: +{
      +  "description": "A short name for this session or window, e.g. \"Claude Code c--ws 33edc07d\". Pass the same one on every call. Every window you open shares this connection, so without it fenbs shows only the connection name and cannot tell your windows apart.",
      +  "type": "string"
      +}
  3. Changed2 schema fields changed
    • addedInput schema / properties / archived
      Added value: +{
      +  "description": "true: archive this Completed task -- off the board, still in search and counts. false: put it back on the board. Only for a task in done (or passed with lane \"done\"). To tidy the whole Completed lane, use fenbs_archive_completed.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / resolution
      Added value: +{
      +  "description": "How a Completed task ended: shipped (the default when it moves to done), wontfix, duplicate, cannotreproduce or obsolete. Only with lane \"done\", or on a task already done.",
      +  "enum": [
      +    "shipped",
      +    "wontfix",
      +    "duplicate",
      +    "cannotreproduce",
      +    "obsolete"
      +  ],
      +  "type": "string"
      +}
  4. Changed2 schema fields changed
    • addedInput schema / properties / full
      Added value: +{
      +  "description": "true: answer with the whole task. Otherwise the ref and what changed.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / whereItStands
      Added value: +{
      +  "description": "Where the work stands right now and what comes next: done so far (commits), not done, next step, anything still running, anything waiting on a person. Short; overwritten each time, the old text kept in History. Plan says how; this says where it is. \"\" clears it. To save several tasks at once, use fenbs_save_progress.",
      +  "type": "string"
      +}
  5. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations (idempotentHint=true, destructiveHint=false), it discloses permission requirements ("needs permission to move tasks", "permission to edit tasks"), preservation semantics for replaced content ("it replaces the old one, which is kept"), the archived lifecycle (only Completed tasks, ref and history retained, still searchable), and claim-release behavior for release/takeover. Nothing here contradicts the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, but the rest is a single unstructured block that jumps between unrelated fields with no grouping, which hurts scanability for a 26-parameter tool. Several sentences duplicate schema descriptions that already carry 88% coverage (resolution, testStatus, size, whereItStands), so not every sentence earns its place.

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?

For a 26-parameter mutation tool with no output schema, it covers the critical gaps: permissions, defaults, replace-vs-merge behavior for plan/steps/links, and cross-tool routing for bulk operations. Error behavior (an unknown ref, a permission denial) is never described, and the output contract is left to the annotations, which is a minor gap given no output schema exists.

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 88%, so the baseline is 3, but the description adds defaults and intent the schema does not: "Leaving resolution out when moving to done still defaults to shipped", "xl means split it", and the relatesTo/unrelate merge-vs-replace distinction. Much of the remaining text (resolution, testNotes, testStatus, archived) restates schema descriptions, so it is additive rather than transformative.

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?

The opening "Change a task by ref. Only the fields passed change." states a specific verb (change), resource (task, identified by ref) and the partial-update semantics that distinguish it from fenbs_create_item and fenbs_delete_item. Sibling differentiation is present but scattered rather than stated up front (fenbs_save_progress for multiple tasks, fenbs_archive_completed for bulk archiving).

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?

It gives conditional guidance for individual fields (when to pass release, takeover, archived, doneSteps vs steps) and names alternatives explicitly: "To save several tasks at once, use fenbs_save_progress" and "To tidy the whole Completed lane, use fenbs_archive_completed." It never states when *not* to call this tool overall (e.g., use create_item for new work), so it stops short of full when/when-not coverage.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources