Skip to main content
Glama

Get StewAI Run Diagnostics

get_run_diagnostics
Read-onlyIdempotent

Read settled billing diagnostics for one owned run.

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": {
      "run_id": "<run_id>"
    },
    "name": "get_run_diagnostics"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is fully covered elsewhere. The description does add real context beyond that: 'settled' is a state precondition and 'owned' is an authorization constraint, but it does not say what happens when a run is not settled or not owned. Useful additions, compressed into two adjectives.

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?

A single nine-word sentence with the resource and both scoping constraints front-loaded and zero filler. Brevity here is close to under-specification, but nothing superfluous is present.

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?

An output schema exists, so return shape needn't be described, and the single-input surface is simple. Still, for a billing-diagnostics tool whose central concept is 'settled', the description gives no hint of what settling means, when diagnostics become available, or how the caller should react to an unsettled run — enough is missing to leave ambiguity at call time.

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 0% — run_id carries only a 26-character pattern with no description — so the description must supply meaning, and it adds that the run must be owned and that exactly one is targeted. It does not clarify the ID format, provenance, or what an invalid/unowned ID yields, so the compensation is partial.

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?

States a specific verb and resource ('Read settled billing diagnostics') scoped to 'one owned run', so the agent knows this returns per-run billing diagnostic data rather than general run state. It is distinguishable from generic siblings like get_run and from recipe-level billing siblings, though it never names any of them.

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?

The qualifiers 'settled' and 'owned' implicitly gate when the tool is valid — only for runs whose billing has reconciled and only for runs the caller owns — but the description never says so explicitly, nor names an alternative (e.g. get_run or get_recipe_activity_billing) for unsettled or aggregate cases. Usage is inferable but not spelled out.

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