Skip to main content
Glama

body_workflow_report

Retrieve an evidence-backed workflow report that shows goals, observations, decisions, actions, verification, and blockers so final answers cite concrete evidence instead of impressions.

Instructions

The evidence-backed report of a workflow (empty id = the latest one).

Shows the goal, what was observed, what was decided, what was done, what was verified and what blocked it - so the final answer cites evidence, not impressions.

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

Input Schema

NameRequiredDescriptionDefault
workflow_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does useful work by enumerating what the report contains (goal, observed, decided, done, verified, blocked) and by disclosing the empty-id fallback behavior, but it never explicitly states that the call is read-only, what happens for an unknown workflow_id, or how large/long the report may be.

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?

Two sentences, front-loaded with the core identity of the tool and followed by the payload description. The long enumeration in the second sentence earns its length by telling the agent what evidence is available, though the em-dash chain is slightly dense.

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 one-parameter read tool with no output schema, the description is nearly complete: it covers purpose, default behavior, and report contents. Missing only the provenance of workflow_id values and confirmation that the operation is non-mutating.

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 0% and the single parameter is undocumented in the schema, so the description must compensate: it does by defining the empty-string default as 'the latest one', which is the one non-obvious semantic an agent needs. It does not describe the id format (where a workflow_id comes from), leaving a small gap.

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 names a specific resource ('the evidence-backed report of a workflow') and states its retrieval semantics (empty id = the latest one), so an agent knows exactly what it returns. It does not differentiate itself from nearby siblings such as body_workflow_note or body_status, which is the only thing keeping it from a 5.

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 implied rather than stated: 'so the final answer cites evidence, not impressions' suggests calling it before composing an answer, and the empty-id default tells the agent it can call with no arguments. There is no explicit when-to-use versus alternatives guidance or statement of prerequisites.

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