Skip to main content
Glama
Sign In
@pooml/mcp

@pooml/mcp

by n0rdy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List metrics

list_metrics
Read-only

List available metric names, types, services, datapoint counts, and last-seen timestamps to identify metrics before running SQL queries.

Instructions

List the metrics this pooml instance has: name, type (counter/gauge), service, datapoint count, last-seen timestamp (ms). Call this before query_metrics when unsure of metric names.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already mark readOnlyHint=true, and the description adds useful output context by specifying the included fields (name, type, service, datapoint count, last-seen timestamp). It does not disclose pagination or empty-list behavior, but those are minor for a read-only listing tool with no parameters.

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: the first states scope and output fields, the second gives usage direction. No filler or redundancy.

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 parameterless, read-only listing tool, the description covers what it returns, when to use it, and how it relates to query_metrics. Nothing essential is missing.

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?

This tool has zero parameters, so the baseline is 4 and the description needs no parameter-level elaboration. It instead usefully documents the returned field information.

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 states a specific action ('List the metrics this pooml instance has') and enumerates exactly what is returned. It also implicitly distinguishes itself from query_metrics by positioning this as the metric-discovery operation.

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

Usage Guidelines5/5

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

Provides explicit when-to-use guidance: 'Call this before query_metrics when unsure of metric names.' This clearly routes an agent to the correct tool among its siblings.

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

Deploy Server

Other Tools