Skip to main content
Glama

Diagnose a Berrys agent run

playground_run_diagnose
Read-onlyIdempotent

One report for a run: verdict (succeeded, failed, waiting_approval, running, cancelled), the failed step, the last good step, failed media jobs with errors, and the suggested next action. Read-only.

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": {
      "projectId": "<projectId>",
      "runId": "<runId>"
    },
    "name": "playground_run_diagnose"
  }
}

Input Schema

NameRequiredDescriptionDefault
runIdYesRun ID returned by preparation or execution for this project.
projectIdYesID of the Playground project chosen for this task; obtain it from project creation, an explicit project link or current context.

Output Schema

NameRequiredDescriptionDefault
nextYes
runIdYes
statusYes
missingYes
verdictYes
canvasUrlYes
failedStepYes
agentCreditsYes
lastGoodStepYes
mediaCreditsYes
spentCreditsYes
conversationIdYes
deliveryVerifiedYes
failedDispatchesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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 safety profile is covered; the description reinforces this with 'Read-only' (consistent, not contradictory) and adds real substance by enumerating the report's sections and the exact verdict vocabulary. It stops short of saying what happens on an unknown or expired runId, which keeps it from 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?

A single front-loaded sentence plus a two-word constraint, with zero filler — the verdict vocabulary is the only enumeration and every item named maps to something the agent will act on.

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?

An output schema exists and the parameters are fully described, so the description only needs to frame what the report is for, which it does by naming the verdict states and next-action field. The one gap is that it never explains when a diagnostic read is the right call versus inspecting events directly, leaving a small inference for the agent.

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 coverage is 100% with only two required UUID parameters already documented, including where runId and projectId come from, so the schema carries the load. The description adds no format, sourcing, or scoping detail beyond what the input schema provides; 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?

The description names a specific deliverable (one diagnostic report for a run) and enumerates its contents: verdict with an explicit state list, failed step, last good step, failed media jobs, and a suggested next action. That is distinguishable from raw-event siblings like playground_run_events or action siblings like playground_run_steer without opening any schema.

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: the diagnostic framing ('verdict', 'suggested next action') signals troubleshooting a run, but the description never states when to pick this over playground_run_events, playground_run_delivery, or playground_node_run, and offers no exclusions or prerequisites.

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.