Skip to main content
Glama

get_working_log

Read-onlyIdempotent

El historial de trabajo: las tareas cerradas —hechas y canceladas—, de la más reciente para atrás.

Es lo que contesta "¿qué hice esta semana?". Las abiertas están en
get_tasks; un informe escrito por la IA se pide con generate_report.

CUIDADO CON LA FECHA DE CIERRE: `completed_at` no siempre está. Sólo
algunos caminos la escriben (el cierre del día, este MCP, los recordatorios,
la sincronización con ClickUp); marcar una tarea como hecha desde la app da
vuelta el estado y no la toca. Por eso el orden cae a `updated_at` cuando
falta, y por eso no sirve para contar "cuántas cerré el martes" sin
aclararlo.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMáximo (default: 50)
offsetNo
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
milestones_onlyNoSolo tasks marcadas como milestones

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses a real data caveat: completed_at is only written by some code paths (day close, this MCP, reminders, ClickUp sync) and not by marking done in the app, so ordering falls back to updated_at. It also warns the ordering fallback makes it unreliable for counting tasks closed on a specific day, which is exactly the kind of trap an agent would otherwise fall into.

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?

Well front-loaded: purpose first, then alternatives, then the date caveat in its own emphasized block. It is slightly long for a read tool and the quoted example question plus the parenthetical list of write paths could be trimmed, but every paragraph carries information an agent needs.

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 read-only list tool with no output schema, it covers purpose, alternatives, default ordering, and the key data-quality pitfall. It stops short of explaining the returned fields or pagination behavior, but the schema supplies parameter defaults and the annotations supply the safety profile.

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 80%, so the schema already documents limit, status, workspace_id and milestones_only. The description adds no parameter-level meaning of its own (it never mentions offset, status filtering, or the workspace_id name-vs-UUID behavior); its completed_at/updated_at discussion is about result ordering, not inputs. 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: the history of closed tasks (done and cancelled), ordered most-recent-first. It explicitly distinguishes itself from get_tasks (open tasks) and generate_report, so an agent can separate it from siblings without opening the schema.

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

Usage Guidelines5/5

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

Names the concrete question it answers ('¿qué hice esta semana?') and routes the agent elsewhere for the two adjacent needs: get_tasks for open items and generate_report for an AI-written report. That is explicit when-to-use plus named alternatives.

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