Skip to main content
Glama

get_report

Read-onlyIdempotent

Obtiene el contenido completo de un reporte específico por su ID.

Usar después de get_reports o get_last_report para leer el texto íntegro de un informe.
Retorna: id, report_type, report_date, generated_at, content (texto plano, máx. 15000 chars), word_count.

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": {
      "report_id": "<report_id>"
    },
    "name": "get_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
report_idYesID del reporte (campo 'id' de get_reports)
workspace_idNoUUID del workspace, o su nombre tal como lo dice el usuario ('Acme', 'el personal'). Omitir = TODOS los workspaces de la persona, en una sola llamada

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so safety is covered. The description adds genuine behavioral value beyond that: the returned field list and the 15000-character cap on the content payload, which tells the agent to expect possible truncation. It does not cover failure behavior when an ID is invalid, so a 4 rather than 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?

Three short blocks: purpose, usage sequence, and return shape. Front-loaded with the verb and resource, and every sentence carries distinct information with no filler.

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 simple two-parameter read with no output schema, the description compensates well by enumerating returned fields and disclosing the content size limit. Missing only edge-case guidance such as a non-existent ID or what happens when report_id matches multiple workspaces.

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% and workspace_id is documented in detail in the schema itself (UUID or workspace name, omitted means all workspaces). The description only restates that lookup is by ID and adds no new semantics on report_id vs workspace_id. Baseline 3 is appropriate.

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 ('Obtiene') and resource ('el contenido completo de un reporte específico por su ID'), making clear this is a single-record read distinguished from the list-style siblings. Naming get_reports and get_last_report as predecessors removes any ambiguity about which tool retrieves full content.

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 explicit sequencing guidance: use after get_reports or get_last_report to read the full text of a report. That is a strong when-to-use signal with named alternatives. It stops short of stating exclusions (e.g., don't use for listing or metadata-only needs), so it falls just 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