Skip to main content
Glama
mcp-server

mcp-server

by yasabbasi

metrics_list

Read-only

Lists every published metric in contract order with name, label, unit, and additive flag, helping users identify available data and interpret totals.

Instructions

Every published metric in contract order: its name, display label, unit (usd, count or ratio) and whether it is additive. A metric is additive when summing it across categories and distribution centers gives the total. orders, the session counts and every ratio are not additive, because one order or session can span several slices. Ratios are fractions between 0 and 1, rounded to four places. Call metrics_explain for one metric's full definition.

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": "metrics_list"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
metricsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/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 substantive semantics beyond that: ordering ('contract order'), the closed unit set (usd, count, ratio), the meaning and limits of additivity, and that ratios are 0–1 rounded to four places. These are behavioral facts not expressed in annotations or schema.

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?

Front-loaded with what is returned, then supporting semantics, then the sibling hand-off — good ordering. The additivity explanation runs to two sentences ('orders, the session counts and every ratio are not additive, because one order or session can span several slices'), which is slightly longer than needed but is not filler.

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?

For a zero-parameter, read-only listing tool with an output schema, the only open question an agent could have is how to interpret the fields, and the description answers that (units, additivity, rounding, ordering) plus where to go for detail. Nothing required to call it correctly is missing.

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

Parameters5/5

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

The tool takes zero parameters, so the baseline is 4; it earns the extra point because the description instead spends its space defining the fields the agent will receive and how to interpret them (additive vs. non-additive, ratio rounding), which is the relevant semantic content for a no-arg call.

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 the exact resource ('Every published metric in contract order') and enumerates the returned fields (name, label, unit, additive), so an agent knows precisely what the tool yields without opening the output schema. It also distinguishes itself from metrics_explain by scope: full list vs. one metric's definition.

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 an explicit hand-off rule — 'Call metrics_explain for one metric's full definition' — which tells the agent when to switch tools. It lacks a negative case (e.g., use metrics_breakdown instead when you need values), so it stops short of full when/when-not guidance.

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