Skip to main content
Glama

get_last_report

Read-onlyIdempotent

Obtiene el/los último(s) reportes generados CON su contenido (máx. 5000 chars por reporte).

Usar cuando el usuario quiere leer el reporte más reciente directamente sin pasar por get_reports primero.
Para leer un reporte específico o con más contenido, usar get_report(report_id).
Para listar reportes sin contenido: usar get_reports.

Retorna: id, report_type, report_date, generated_at, content (texto plano hasta 5000 chars), word_count, total_tokens.

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

Input Schema

NameRequiredDescriptionDefault
limitNoNúmero de reportes recientes a devolver (default: 1)
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.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the description doesn't need to restate safety. It does add genuinely new behavioral context: content is truncated at 5000 chars per report, returned as plain text, and the call returns multiple reports when limit > 1. It does not mention permissions or how the workspace is resolved when omitted, which keeps it below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded purpose sentence followed by three short routing lines and a return-field list; every line carries either selection guidance or output information that has no other home. No filler or repetition.

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?

With no output schema, the description supplies the return fields (id, report_type, report_date, generated_at, content, word_count, total_tokens), which is exactly what an agent needs to consume the result. For a two-optional-param read tool with full annotation coverage, nothing material is missing.

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 description coverage is 100%, so both limit and workspace_id are already documented in the schema (including the default of 1 and the UUID-or-name flexibility). The description adds only indirect meaning about how many reports come back, so 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?

'Obtiene el/los último(s) reportes generados CON su contenido' states a specific verb (obtener), resource (reportes) and scope (el más reciente, con contenido). It immediately distinguishes itself from get_report and get_reports, which are named explicitly.

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?

It gives an explicit when-to-use ('cuando el usuario quiere leer el reporte más reciente directamente sin pasar por get_reports primero') plus two named alternatives with the condition that selects each: get_report(report_id) for a specific report or more content, get_reports for listing without content.

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