Skip to main content
Glama

score_delivery_health

Read-onlyIdempotent

Use when assessing one service’s DORA and flow evidence for an internal delivery dashboard. Returns five DORA measures, sample sizes, missing-data caveats and practical evidence-collection actions; remote calls accept aggregate reports 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": {
      "metrics": "<metrics>"
    },
    "name": "score_delivery_health"
  }
}

Input Schema

NameRequiredDescriptionDefault
metricsYes

Output Schema

NameRequiredDescriptionDefault
resultYes
generatorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior. The description adds useful behavioral context: it summarizes returned evidence (sample sizes, missing-data caveats, evidence-collection actions) and states the aggregate-report input constraint. It does not cover auth or rate limits, but with annotations that is acceptable.

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, front-loaded with the usage condition and followed by return and constraint details. No filler.

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

Completeness2/5

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

For a complex nested input with no schema descriptions, the definition is too thin: it does not explain how to populate the metrics object or reconcile the 'five DORA measures' summary with the 11 required metric fields. Output schema exists, so return values need less explanation, but input completeness is still weak.

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?

Schema description coverage is 0% and the single metrics parameter is a deeply nested object with 11 required metric entries. The description only says 'aggregate reports only' and does not explain the required metric fields, units, period structure, or caveats, so it leaves most parameter meaning to the schema’s property names.

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 the domain (one service’s DORA and flow evidence) and the dashboard context, so the agent can distinguish this delivery-health scoring tool from the AI-readiness/cost siblings. It does not explicitly restate the scoring verb, but the purpose is still clear.

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 gives a clear when-to-use condition ('assessing one service’s DORA and flow evidence for an internal delivery dashboard') and a constraint ('remote calls accept aggregate reports only'). It does not name when not to use it or point to an alternative, so it falls short of 5.

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.