Skip to main content
Glama

generate_report

Destructive

Genera un nuevo reporte/informe de IA del workspace analizando notas diarias, tareas completadas y actividad reciente.

Este proceso tarda ~15-30 segundos. Una vez completado, el reporte queda guardado y disponible en get_reports/get_last_report.

Tipos:
- 'daily' (default): resumen del día actual, tasks completadas hoy, notas del día
- 'weekly': resumen de la semana, tendencias, highlights
- 'monthly': análisis mensual completo (más tokens, más tiempo)

Usar cuando el usuario pide "generá un reporte", "hacé un informe del día/semana", etc.
Retorna el contenido del reporte generado directamente.

Fuera de Secondbrain: el informe se manda por mail al dueño del workspace. Si ya había uno del mismo tipo ese día, lo reemplaza.

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": "generate_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
report_typeNoTipo de reporte a generar (default: daily)
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

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses a 15-30 second runtime, that the result is persisted and then reachable via get_reports/get_last_report, that monthly is heavier in tokens and time, and that outside Secondbrain an email is sent to the workspace owner. The "si ya había uno del mismo tipo ese día, lo reemplaza" note concretely explains the destructiveHint=true annotation rather than contradicting it.

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 purpose and cost, then a scannable bulleted type list, then trigger conditions and side effects. Slightly longer than strictly necessary — the return-content sentence and the header sentence overlap a bit — but no section is wasted.

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 two-parameter, non-idempotent, open-world mutation with no output schema, the description covers everything an agent needs: cost/latency, persistence and retrieval path, overwrite semantics, external email side effect, and mode selection. Nothing material is left to inference.

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 already 100%, so the baseline is 3, but the description adds real meaning to report_type by defining what each mode covers (daily = today's summary/tasks/notes, weekly = trends and highlights, monthly = fuller analysis at higher cost). workspace_id gets no treatment beyond the schema's own note about omitting it when the token is workspace-scoped.

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 ("Genera un nuevo reporte/informe de IA del workspace") and immediately scopes the inputs it analyzes (notas diarias, tareas completadas, actividad reciente). It also distinguishes itself from the retrieval siblings by naming get_reports/get_last_report as the place the finished artifact lives.

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 an explicit trigger ("Usar cuando el usuario pide 'generá un reporte'...") and implicitly routes read-only needs to get_reports/get_last_report by framing this tool as generation-only. It lacks an explicit "do not use when a report already exists" rule, which matters given the overwrite behavior, so it stops short of a 5.

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