Skip to main content
Glama

get_deliverables

Read-onlyIdempotent

Los entregables del workspace, con cuántas tareas tiene cada uno abiertas y cerradas.

Un entregable es la cosa que se entrega —una propuesta, un informe, una
campaña— y las tareas cuelgan de él. Sirve para contestar "¿cómo viene X?"
sin leer tarea por tarea.

El `summary` lo escribe la IA a partir de lo que pasó; `delivered_at` es
cuándo se entregó de verdad.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_deliverables"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMáximo (default: 50)
statusNoFiltrar por estado
workspace_idNoUUID del workspace, o su nombre tal como lo dice el usuario ('Acme', 'el personal'). Omitir = TODOS los workspaces de la persona, en una sola llamada

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds genuinely new behavioral context: the `summary` field is AI-generated from what happened (a provenance/reliability caveat) and `delivered_at` is the real delivery date. It omits pagination/limit behavior, keeping it from a 5.

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?

The payload description is front-loaded in the first line, followed by a short definition and field notes. Every sentence carries information, though the definitional paragraph could be trimmed slightly for a purely operational reader.

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?

With no output schema, the description carries the burden of explaining returns and does so for the key fields (open/closed task counts, summary, delivered_at). Gaps remain on pagination behavior and what values `status` accepts, but the tool is a simple read and is largely self-explanatory.

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 100%, including the important note that omitting workspace_id returns ALL of the person's workspaces in one call. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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 description names a specific resource (entregables/deliverables) and states the returned payload precisely: each deliverable with its count of open and closed tasks. It also defines what a deliverable is, which removes ambiguity. It does not distinguish itself from sibling listing tools (e.g. get_artifact, get_documents), 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 Guidelines4/5

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

It gives a clear use case — answering "¿cómo viene X?" without reading task by task — which tells the agent this is a rollup/summary view rather than a task detail fetch. There are no explicit exclusions or named alternatives, so it is context-rich but not fully routing guidance.

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