Skip to main content
Glama

Boletín Claro

by es.boletinclaro

Anotar una entrada

anotar_entrada

Escribe una nota en una de tus entradas: lo que hay que hacer, lo que ya se ha hecho o lo que conviene recordar sobre esa oportunidad. Indica 'entrada_id' (el 'id' que aparece en listar_entradas o mis_novedades) y 'nota'. Si añades 'fecha' (AAAA-MM-DD), la nota se convierte en un vencimiento del calendario y se avisa por email 7 días antes y el día antes: úsala para plazos de presentación, reuniones o recordatorios. Con 'cliente' (opcional, solo modo clientes) la nota queda bajo ese cliente en vez de a la vista de todo el espacio de trabajo. Es la misma nota que se ve en boletinclaro.es. Requiere iniciar sesión.

Input Schema

TableJSON 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.
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 o mis_novedades (campo 'id').

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the minimal annotation (destructiveHint=false), the description discloses key behaviors: the note becomes a calendar due date with email reminders if fecha is provided, notes are visible on boletinclaro.es, and the optional cliente parameter scopes visibility. No contradiction with annotations.

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 description is a single paragraph that starts with a clear main purpose, then explains parameters with examples. It is reasonably concise, though could be slightly more structured with bullet points. No wasted sentences.

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 mutation tool with 4 parameters and no output schema, the description covers parameter usage, side effects (email reminders), and visibility. It does not explain return values, but that is acceptable for non-query tools. Annotations complement safety.

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?

All parameters have schema descriptions (100% coverage), and the tool description adds extra context: examples for nota, explanation of fecha's email notification behavior, and the client scoping effect of cliente. This adds value beyond 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?

The description clearly states the tool creates a note on an entry, using specific verbs ('escribe una nota') and identifying the resource ('entrada'). It also differentiates from siblings like borrar_nota and listar_notas by detailing what this tool does.

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?

The tool explains when to use it (to add notes, reminders, etc.) and provides context for optional parameters (fecha for calendar reminders, cliente for client scoping). However, it does not explicitly contrast with sibling tools or state when not to use it.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool targets a distinct action or resource: search vs. detail vs. alerts vs. company profile. No two tools overlap in purpose; even alert management tools (create, edit, pause, reactivate, delete) are clearly differentiated via descriptions and parameters.

Naming Consistency5/5

All tools follow a consistent Spanish verb_noun pattern (e.g., buscar_boletines, crear_alerta, pausar_alerta) with imperative verbs. The pattern is uniform across all 16 tools, enhancing predictability for an agent.

Tool Count4/5

With 16 tools, the count is slightly above the ideal range (3-15) but fully justified by the breadth of the domain: search, details, alerts lifecycle, company data, and summaries. Each tool serves a distinct need without unnecessary bloat.

Completeness5/5

The tool surface covers the full lifecycle of monitoring public money: searching (boletines, oportunidades, empresas), getting detailed information (convocatoria, licitacion, perfil), managing alerts (CRUD plus pause/reactivate), and summarizing (resumen_boletin, resumen_semana, mis_novedades). No obvious gaps.

Resources