Skip to main content
Glama

create_deliverable

Crea un entregable. Para colgarle tareas, pasá su id en deliverable_id al crear o actualizar cada tarea.

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

Input Schema

NameRequiredDescriptionDefault
nameYesQué se entrega
statusNoEstado inicial
workspace_idNoUUID del workspace, o su nombre tal como lo dice el usuario ('Acme', 'el personal'). Omitir si el token ya tiene workspace fijo

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 this is a non-destructive, non-idempotent, non-open-world write, so the safety profile is covered. The description adds genuinely useful non-obvious behavior: tasks are linked to a deliverable by passing its id in deliverable_id. It still says nothing about side effects, naming uniqueness, status defaults, or what is returned.

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 sentences, front-loaded with the core action, with the follow-up workflow note second. Nothing is redundant.

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 simple three-parameter create tool with full schema coverage and annotations, the basics are covered. However, there is no output schema and the description never says the created deliverable's id is returned, even though its own workflow advice depends on obtaining that id.

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%, so name, status, and workspace_id are fully documented, including the name-or-UUID flexibility for workspace_id. The description's only parameter mention is deliverable_id, which is not a parameter of this tool at all, so it adds cross-tool context rather than meaning for its own inputs.

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 and resource ('Crea un entregable'), which is unambiguous on its own. It does not differentiate itself from siblings like create_task or create_canvas beyond the resource name, so it stops short of a 5.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternative is named. Usage is only implied through the follow-up workflow hint about attaching tasks via deliverable_id, which tells the agent what to do after creation but not when to choose this tool.

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