Skip to main content
Glama
Metrx MCP Server

Metrx MCP Server

by metrxbots

Get Agent Health Scores

metrx_get_health_scores
Read-onlyIdempotent

Returns health score, grade, and data completeness for all agents in the organization. Health scores are composite 0-100 scores blending cost efficiency, ROI, error rate, quality drift, failure risk, and latency.

Instructions

Returns health score, grade, and data completeness for all agents in the organization. Health scores are composite 0-100 scores blending cost efficiency, ROI, error rate, quality drift, failure risk, and latency. Grades: A (80-100), B (60-79), C (40-59), D (20-39), F (0-19). Use this for a health overview across all agents. Requires an API key with the 'read' scope.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "metrx_get_health_scores"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds genuinely new context beyond that: the composite inputs behind the score, the grade band mapping, the presence of a data-completeness field, and the 'read' scope API key requirement.

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?

Four sentences, front-loaded with the return content, then the score composition, then the grade bands, then the usage cue and auth requirement. Every sentence carries information an agent needs to interpret or call the tool; nothing is redundant with the annotations.

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?

There is no output schema, so the description must describe return values, and it does: score, grade, data completeness, plus the numeric grade thresholds needed to interpret a grade. Combined with the auth requirement, an agent has everything needed to call and read the result.

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

Parameters4/5

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

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly avoids inventing filtering options that the empty schema does not support.

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?

States a specific verb and resource ('Returns health score, grade, and data completeness') plus an explicit scope ('for all agents in the organization'), which cleanly separates it from the single-agent sibling metrx_get_agent_detail. An agent can identify the tool without opening the schema.

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?

Provides a clear usage cue: 'Use this for a health overview across all agents.' That establishes the intended context, but it does not name an alternative for per-agent drill-down or state when this tool should be avoided, so it stops short of full routing guidance.

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