Skip to main content
Glama

reopen_day_note

DestructiveIdempotent

Reabre la nota diaria de una fecha, igual que en la app: deshace el cierre y borra las tareas que ese cierre había creado. Fuera de Secondbrain: las tareas del cierre que ya estaban en ClickUp o Jira se sacan o se cierran allá.

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

Input Schema

NameRequiredDescriptionDefault
dateYesFecha en formato YYYY-MM-DD
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.9/5.0
Behavior4/5

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

Annotations already flag destructive=true, idempotent=true and openWorld=true, so the bar is lower; the description still adds real value by naming what is destroyed (the tasks created by the closure) and disclosing that ClickUp/Jira tasks get removed or closed in the external system. It stops short of stating permission requirements or what happens if the day was never closed.

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?

Two tight sentences with the core action front-loaded and the external-system consequence second. No filler, though 'igual que en la app' is decorative rather than informative.

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 destructive, open-world mutation with full schema coverage and no output schema, the description covers the main risk (task deletion) and the cross-system side effect. Only edge-case behavior (reopening a day that was never closed, required permissions) is left implicit.

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% and both parameters (date in YYYY-MM-DD, workspace_id UUID or name) are already documented in the schema; the description adds no extra parameter meaning, 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?

States a specific verb and resource ('Reabre la nota diaria de una fecha') plus the exact effects ('deshace el cierre y borra las tareas que ese cierre había creado'), which makes it the clear inverse of close_day_note without needing to open 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 Guidelines3/5

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

The 'igual que en la app' framing and the external-system caveat imply when this is appropriate, but there is no explicit when-to-use / when-not-to-use statement or a named alternative (e.g. a plain note edit for cases where no closure exists).

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