Skip to main content
Glama

update_deliverable

DestructiveIdempotent

Cambia el nombre, el estado o la fecha de entrega de un entregable.

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": {
      "deliverable_id": "<deliverable_id>"
    },
    "name": "update_deliverable"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
statusNo
delivered_atNoCuándo se entregó (ISO), o null
workspace_idNoUUID del workspace, o su nombre tal como lo dice el usuario ('Acme', 'el personal'). Omitir si el token ya tiene workspace fijo
deliverable_idYesID del entregable

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds nothing beyond that: it does not say that omitted fields are left unchanged (partial update), what a destructive edit can overwrite, or whether status changes have side effects. For a destructive mutation, this leaves meaningful behavioral gaps.

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?

A single well-formed sentence with the resource and editable fields front-loaded and no filler. It is efficient, though minimal enough that conciseness borders on under-specification.

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

Completeness2/5

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

For a destructive, multi-parameter mutation with no output schema, the description should clarify partial-update semantics, the optional workspace_id scoping, and consequences of changing status or delivered_at. None of that is present, so an agent cannot fully predict the tool's effect from the definition.

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 60%, with delivered_at and workspace_id documented in the schema. The description names name, status and delivered_at but omits workspace_id entirely, and adds no format or allowed-value detail for status beyond what the schema provides. Baseline 3 is appropriate.

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 ('Cambia') and resource ('un entregable') plus the three editable fields, so the operation is unambiguous. It does not differentiate from the many sibling update_* tools (update_task, update_document, update_clip, etc.), which is the main clarity gap.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus create_deliverable or the other update_* siblings, and no prerequisites are stated. The only implicit cue is that it edits an existing deliverable, which the agent must infer.

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