Skip to main content
Glama
Orchestra MCP Server

Orchestra MCP Server

Official
by orchestra-hq

Diagnose Task Run

diagnose
Read-only

Investigate one failed task run by reviewing its status, messages, parameters, upstream task statuses, newest log tail, and artifact filenames to pinpoint what went wrong.

Instructions

Deep dive on one failed task run: its status and messages, taskParameters and runParameters, the statuses of the upstream tasks it depends on, the tail of its newest log, and its artifact filenames. Over-long parameter values, the log tail and the artifact list are capped, and the response says which parts were cut. Use download_task_run_log or download_task_run_artifact when the tail is not enough.

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": {
      "task_run_id": "<task_run_id>"
    },
    "name": "diagnose"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_idNoAct on this account rather than the one the credential resolves to. Omit it to use the credential's own account. An API key is issued to a single account, so it may only name that account; an OAuth token may name any account its grant covers.
task_run_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.1
    • addedInput schema / properties / account_id
      Added value: +{
      +  "anyOf": [
      +    {
      +      "format": "uuid4",
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Act on this account rather than the one the credential resolves to. Omit it to use the credential's own account. An API key is issued to a single account, so it may only name that account; an OAuth token may name any account its grant covers."
      +}
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With readOnlyHint already declared, the description still adds real behavioral value: it discloses that over-long parameter values, the log tail and the artifact list are capped, and that the response flags which parts were cut. That truncation contract is exactly the kind of thing an agent cannot infer from annotations or schema.

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?

Two sentences, zero filler, with the returned-content inventory front-loaded and the escalation path to download tools placed last where it belongs.

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, so return shape need not be restated, and the truncation caveat covers the main behavioral risk. Minor gap: it does not say whether the tool works on non-failed runs or how it relates to get_task_run for a successful run.

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 50%: account_id is fully documented in the schema, while task_run_id has no description at all. The tool description never mentions parameters, so it relies on task_run_id being self-evident from the purpose statement — adequate but not compensating for the coverage gap.

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 verb ('Deep dive on one failed task run') and then enumerates exactly what is returned: status and messages, taskParameters and runParameters, upstream task statuses, log tail, artifact filenames. An agent can immediately tell this is an aggregated diagnostic read rather than a raw fetcher like get_task_run.

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?

It explicitly routes to alternatives with a condition: 'Use download_task_run_log or download_task_run_artifact when the tail is not enough,' and scopes itself to failed runs. It does not clarify how it differs from the sibling get_task_run, which is the main remaining ambiguity.

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

Deploy Server

Other Tools