Skip to main content
Glama

get_declared_tasks

Read-onlyIdempotent

Las tareas que están escritas en las notas diarias pero todavía no son tareas de verdad: las PROVISORIAS.

Un renglón de la nota que parece un pedido se levanta como segmento con lo
que se le pudo sacar (título, urgencia, responsable, proyecto) y una
confianza. Mientras nadie lo confirme no hay fila en `tasks`: por eso no
aparece en get_tasks. Cuando se confirma, `db_task_id` apunta a la tarea
real.

`missing_date` y `missing_owner` son lo que quedó sin declarar — es la
razón por la que una provisoria se queda esperando.

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_declared_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMáximo (default: 50)
note_dateNoSólo las de esta nota, YYYY-MM-DD
pendientesNoSólo las que no se confirmaron ni descartaron (default: true)
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

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, non-open-world, so the bar is lower; the description still adds meaningful behavior—that no row exists in `tasks` until confirmation, that `db_task_id` links to the real task, and that `missing_date`/`missing_owner` explain why a provisional stays waiting. Return shape is sketched but pagination/ordering isn't mentioned.

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?

Front-loaded with the core definition and broken into short paragraphs that each carry information. Some phrasing is colloquial/roundabout ('con lo que se le pudo sacar'), a minor cost, but nothing is wasted outright.

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 return-value burden and does so by naming key fields (título, urgencia, responsable, proyecto, confianza, db_task_id, missing_date, missing_owner). Ordering/pagination behavior is the only notable gap for a four-param read tool.

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%, so the schema already documents limit, note_date, pendientes, and workspace_id with useful hints (defaults, UUID or name, omit = all workspaces). The description adds no parameter-specific meaning beyond the schema, so the 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?

The description names a specific resource (tareas PROVISORIAS extraídas de notas diarias) and explicitly distinguishes it from the sibling get_tasks ('por eso no aparece en get_tasks'). An agent can immediately tell this returns extracted-but-unconfirmed line items, not real tasks.

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?

Usage is well routed: it explains the alternative (get_tasks) and the condition that separates them (unconfirmed vs. confirmed with db_task_id). It lacks an explicit 'use this when...' sentence and says nothing about when not to call it, but the context is unambiguous.

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