Skip to main content
Glama

Update a blueprint task

blueprint_update_task
DestructiveIdempotent

Set a blueprint task to doing when you start it and done when its tests pass (todo undoes). It replaces the task's status and is safe to repeat; a task still blocked_by others is set too, with a warning. An unknown task_id answers task_not_found. Your human sees the progress on the plan page.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "status": "doing",
      "task_id": "build-signup",
      "instance_id": "bpr_exampleexampleexample2"
    },
    "name": "blueprint_update_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusYesdoing when you start, done when its tests pass, todo to undo.
task_idYesTask id from blueprint_tasks.
instance_idYesUtility instance id from buy or list_utilities.
passport_tokenNoYour amp_ token, only if you have no app sign-in and cannot send a header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "instance_id": "bpr_exampleexampleexample2",
      +    "status": "doing",
      +    "task_id": "build-signup"
      +  }
      +]
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."New value: +"Your amp_ token, only if you have no app sign-in and cannot send a header."
  2. Changed4 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."New value: +"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."
    • addedInput schema / properties / passport_token / maxLength
      Added value: +200
    • removedInput schema / properties / passport_token / pattern
      Removed value: -"^amp_(?:s_)?[A-Za-z0-9_-]{43}$"
  3. Changed4 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / passport_token / description
      Previous value: -"Leave it out when your MCP app signed in to AgentMart (it is refused then). Otherwise your passport bearer token (amp_...) or session token (amp_s_...), only if your client cannot send it as an Authorization header. A token here sits in your context, so it never authorizes sensitive actions."New value: +"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."
    • addedInput schema / properties / status / description
      Added value: +"doing when you start, done when its tests pass, todo to undo."
    • addedInput schema / properties / task_id / description
      Added value: +"Task id from blueprint_tasks."
  4. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare idempotentHint and destructiveHint, and the description reinforces but also extends them: 'replaces the task's status' clarifies overwrite semantics, blocked tasks are still set with a warning, and unknown task_id yields task_not_found. It adds real error and side-effect context beyond the annotations, though return shape is unaddressed (no output schema).

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?

Four tight sentences with the core action front-loaded and no filler. The closing line about the human seeing progress is minor color but does convey a visibility side effect, so it 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 4-parameter mutation tool with no output schema, the description covers lifecycle semantics, idempotency, blocking warnings, and the not-found error. Only the response shape and passport_token fallback behavior are left implicit, which is a small gap.

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 coverage is 100% and every parameter, including the status enum and passport_token fallback, is documented in the schema. The description's status wording largely restates the status field description, so it adds little new meaning; baseline 3 applies.

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?

States a specific verb and resource ('Set a blueprint task to doing/done/todo') and immediately scopes it to status mutation, which is clearly distinct from the listing/structural siblings like blueprint_tasks and blueprint_put_stage.

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?

Explains when to use each status value ('doing when you start it', 'done when its tests pass', 'todo undoes'), which is genuine when-to-use guidance. It doesn't name an alternative tool or state when not to call it, so it falls just short of a 5.

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.