Skip to main content
Glama

Agent run outcome analysis

privi_pro_run_health_summary
Read-only

Aggregate completed agent task statuses and elapsed time. PAID ONLY: 5 prepaid credits; production billing required.

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": {
      "runs": "<runs>"
    },
    "name": "privi_pro_run_health_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
runsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description usefully adds the billing model (5 prepaid credits, production billing required), which is real behavioral context an agent cannot infer. It does not disclose output shape, per-run vs aggregate granularity, or any limit on how many runs can be submitted, leaving meaningful gaps.

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 tight sentences with no filler; the functional purpose is front-loaded and the cost constraint follows. Every clause carries information the agent cannot get from structured fields.

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

Completeness5/5

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

Placeholder

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one required parameter, 'runs', with 0% schema description coverage — the array's element structure is entirely undefined. The description says only 'completed agent task statuses', giving a hint about content but no field names, formats, or constraints the agent needs to construct a valid call.

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 concrete verb and resource: aggregating completed agent task statuses plus elapsed time. It is clear what the tool computes, though it offers no differentiation from the many sibling analysis primitives (error_budget, latency_slo, etc.) that an agent might confuse it with.

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

Usage Guidelines2/5

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

No guidance on when to use this versus alternatives, no prerequisites beyond billing, no exclusions. The only routing-relevant information is the cost note, which tells the agent when NOT to call it (if unpaid) but nothing about fit relative to sibling analyses.

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.