Skip to main content
Glama
Sign In

Boletín Claro

by es.boletinclaro
OverviewDiscussionsAdmin

Anotar una entrada

anotar_entrada

Escribe una nota en una de tus entradas: lo que hay que hacer, lo hecho o lo que conviene recordar. Indica 'entrada_id' (de listar_entradas) y 'nota'. Con 'fecha' (AAAA-MM-DD) sale en el calendario y se avisa por email antes; un plazo legal lo calcula la herramienta plazo. Con 'cliente' (modo clientes) queda bajo ese cliente. Es la misma nota que se ve en boletinclaro.es. Requiere iniciar sesión. Coste: 0.

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": {
      "entrada_id": "<entrada_id>",
      "nota": "<nota>"
    },
    "name": "anotar_entrada"
  }
}

Input Schema

NameRequiredDescriptionDefault
notaYesTexto de la nota: qué hay que hacer, qué se ha hecho o qué recordar sobre esta oportunidad. Ej: 'Presentada la solicitud, falta el certificado de la Seguridad Social'.
fechaNoOpcional. Fecha del vencimiento o evento en formato AAAA-MM-DD (ej: 2026-09-15). Si la pones, la nota aparece en el calendario y se avisa por email 7 días antes y el día antes.
sobreNoOpcional, expediente: paso:<id>, documento:<id> o nota:<id> que comenta
clienteNoOpcional (solo modo clientes). Nombre del cliente bajo el que archivar la nota, tal como aparece en listar_clientes. Sin este campo la nota es de la entrada y la ve todo tu espacio de trabajo.
entrada_idYesId de la entrada a anotar, tal como aparece en listar_entradas (campo 'id').

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / entrada_id / description
      Previous value: -"Id de la entrada a anotar, tal como aparece en listar_entradas o mis_novedades (campo 'id')."New value: +"Id de la entrada a anotar, tal como aparece en listar_entradas (campo 'id')."
  2. Changed1 schema field changed
    • addedInput schema / properties / sobre
      Added value: +{
+  "description": "Opcional, expediente: paso:<id>, documento:<id> o nota:<id> que comenta",
+  "type": "string"
+}
  3. Added

TDQS

A4.1/5.0
Behavior4/5

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

The only annotation is destructiveHint=false, so the description carries most of the burden and does add real value: login requirement, zero cost, calendar appearance and email reminders for fechas, workspace-wide visibility versus client-scoped visibility with 'cliente', and that the note surfaces on boletinclaro.es. It does not describe what happens on duplicate or conflicting notes, and it doesn't state whether the write is reversible.

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 core action and its required parameters are front-loaded, followed by optional-parameter consequences and operational facts, with no filler sentences. It is dense and slightly run-on in places, but every clause conveys usable information.

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 5-parameter write with no output schema and minimal annotations, the description covers visibility, side effects (calendar, email), auth, and cost, which is enough to call it safely. The omission of the 'sobre' parameter and of any error/conflict behavior keeps it from being fully complete.

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 the description largely restates the same field semantics (entrada_id from listar_entradas, AAAA-MM-DD format, cliente for 'modo clientes'). It adds some downstream consequences the schema only partially hints at, but it never mentions the 'sobre' parameter (expediente target), leaving one field's role to the schema alone.

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 ('Escribe una nota en una de tus entradas') and enumerates the note's purposes (to-do, done, reminder). It also distinguishes itself from the legal-deadline sibling by noting 'un plazo legal lo calcula la herramienta plazo', so an agent can route correctly 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 Guidelines4/5

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

Gives clear when-to-use context (annotate an existing entrada located via listar_entradas) and an explicit exclusion pointing legal deadlines to the plazo tool. It lacks guidance on cases like appending to an existing note vs creating a new one, or when to prefer borrar_nota/ver_entrada, so it does not reach a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Boletín Claro toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources