Skip to main content
Glama

Get report

get_report

Retrieve the last integration report or one flow's steps with full evidence, including requests, messages, queries, and job output, to support QA verification and CI release decisions.

Instructions

The last integration report, or one flow's steps with full evidence (requests, messages, queries, job output).

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

Input Schema

NameRequiredDescriptionDefault
flowNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations at all, the description carries the disclosure burden; it does communicate that the payload includes concrete evidence (requests, messages, queries, job output), which is genuinely useful since no output schema exists. It does not state what happens when no report exists, whether results are cached/refreshed, or how large the evidence payload can get.

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?

One compact sentence with the default behavior front-loaded and the per-flow detail following. It is a noun-phrase fragment rather than a verb-led statement, which slightly weakens the opening, but nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-optional-parameter read tool with no annotations and no output schema, the description covers the essentials of what is returned and how the argument changes the result. Two gaps remain: the format of a flow identifier and the empty-state behavior when no report has been produced yet.

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 description coverage is 0%, so the description must compensate, and it does: the phrase "the last integration report, or one flow's steps" makes clear that the single optional flow argument switches between the default summary and a per-flow drill-down. It still does not say what form a flow identifier takes (name, ID, path).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the resource (integration report) and the two modes it covers: the most recent report, or one flow's steps with full evidence. An agent can tell it retrieves reporting data rather than mutating config, but it never contrasts itself with siblings like run_integration_tests or validate_flow, which also produce diagnostic-ish output.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is only implied through the two described modes: omit the flow argument for the last report, supply one for per-flow detail. There is no explicit statement of when to prefer this over running or validating an integration, and no exclusions or preconditions (e.g., whether a report must already exist).

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