Skip to main content
Glama
mcp-server

mcp-server

by yasabbasi

metrics_explain

Read-only

Returns the full definition of a specified metric, including unit, aggregation, and formula, so you can interpret and explain its values correctly.

Instructions

The full definition of one metric: its name, display label, unit (usd, count or ratio), whether it is additive, a plain-language description, its aggregation (sum, count, count_distinct or ratio) and its formula. Ratios are fractions between 0 and 1, rounded to four places. Call it before explaining what a number means. Call metrics_list for the valid names.

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

Input Schema

NameRequiredDescriptionDefault
nameYes

Output Schema

NameRequiredDescriptionDefault
nameYes
unitYes
labelYes
formulaYes
additiveYes
aggregationYes
descriptionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/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 the safety profile is covered. The description adds one genuinely useful behavioral detail — that ratios are fractions between 0 and 1 rounded to four places — but says nothing about failure behavior for an unknown name or about performance/caching.

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?

One dense sentence front-loads the returned fields, followed by two short routing sentences; nothing is padding. The field enumeration overlaps the existing output schema, which is mild redundancy, but it also surfaces the unit/aggregation enum values inline, which justifies its length.

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?

For a one-parameter read tool with an output schema, the description covers what the tool does, when to call it, and where valid names come from. The main residual gap is error behavior for a bad name, which is minor given the `metrics_list` pointer.

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?

The single `name` parameter has 0% schema description, so the description must compensate. It does so partially by pointing to `metrics_list` as the source of valid names, which is real value, but it never states accepted format, case sensitivity, or what happens on an invalid name.

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 resource and scope ('the full definition of one metric') and enumerates exactly what is returned (name, label, unit, additive, description, aggregation, formula). It also distinguishes itself from siblings by directing name lookup to `metrics_list`.

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 trigger ('Call it before explaining what a number means') and routes the agent to `metrics_list` for valid names. It stops short of stating when this tool is unnecessary (e.g. if only a current value is needed), but the guidance is actionable.

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