Skip to main content
Glama

get_agenda

Read-onlyIdempotent

La agenda de un día o de varios, en UNA llamada: los eventos del calendario, las tareas que vencen, las vencidas que siguen abiertas y los recordatorios que van a sonar. Es «¿qué tengo hoy?», «¿qué tengo mañana?» y «¿qué tengo esta semana?» contestadas de una vez, en vez de get_events + get_tasks cruzadas a mano.

Sin `workspace_id` junta TODOS los workspaces de la persona (cada cosa dice
de cuál es): no la llames una vez por workspace. Para varios días pasá
`hasta` (la semana: `date` el lunes, `hasta` el domingo): no la llames un
día por vez, ni le sumes get_events o get_tasks para lo mismo.

Sin `date`, es hoy en la zona horaria del usuario — que no es la de UTC: en
Buenos Aires, hasta las 21hs, UTC ya está en el día siguiente.

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

Input Schema

NameRequiredDescriptionDefault
dateNoYYYY-MM-DD (default: hoy, en la zona del usuario). Con hasta, el primer día
hastaNoYYYY-MM-DD, último día inclusive, para ver varios días de una (hasta 31)
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.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, but the description adds operational behavior the annotations cannot convey: omitting workspace_id fans out across ALL of the person's workspaces with provenance on each item, and the default date resolves in the user's timezone rather than UTC, illustrated with the Buenos Aires 21hs case. It also caps the multi-day span at 31 days. This is the kind of pitfall context that prevents wrong calls.

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 capability and its payoff, then the aggregation rule, then the date/timezone caveat — a sensible priority order. Slightly repetitive: the 'one call, not per workspace / not per day' idea is restated in both the second and third paragraphs, which could be tightened without losing meaning.

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

Completeness5/5

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

For a zero-required-parameter aggregator with no output schema, the description covers what it returns, how scope behaves with and without workspace_id, the multi-day mechanism and its limit, and the timezone default. Nothing an agent needs in order to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, and the description genuinely goes beyond it by explaining the consequence of omitting workspace_id (all workspaces in one call, not one call per workspace) and by giving a concrete week example for date+hasta (Monday to Sunday). The timezone note reinforces the date default meaningfully. Minor deduction only because the per-parameter format details are largely already in the schema.

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+resource ('La agenda de un día o de varios') and enumerates exactly what it returns: calendar events, tasks due, overdue open tasks, and upcoming reminders. It explicitly positions itself against the sibling pattern 'get_events + get_tasks cruzadas a mano', so an agent can tell it apart from those tools without opening either 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?

Gives explicit when-to-use framing ('¿qué tengo hoy?', 'mañana', 'esta semana') and explicit when-not-to-call rules: do not call once per workspace, do not call day by day, and do not supplement with get_events or get_tasks for the same data. It also names the alternative (get_events + get_tasks) and the condition that selects this tool instead.

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