Skip to main content
Glama

List Metrics

list_metrics
Read-onlyIdempotent

List the metrics kept in a room: named values (such as MRR or open tickets) a widget shows, each with its key, label, format, unit, current value and when the value last changed. Also returns the per-room limit.

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

Input Schema

NameRequiredDescriptionDefault
invite_codeYesRoom invite code.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description adds that results include each metric's current value and last-changed time plus a per-room limit, which is modest extra context, but it says nothing about ordering, pagination, or behavior in an empty room.

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 front-loaded sentence that opens with the verb and resource, then spends its remaining words on the metric shape and the limit. The enumerated field list is slightly dense but every item conveys real information about the payload.

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 full annotation coverage and an output schema, the description covers purpose, the meaning of a metric, and the extra limit value. Nothing critical is missing; only edge-case behavior and ordering are left unstated.

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?

There is a single parameter with 100% schema description coverage ('Room invite code.'), so the schema already carries the meaning and the description adds nothing about scope, validity, or what happens with an invalid invite code. Baseline 3 applies.

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 ('List the metrics kept in a room') and then defines what a metric actually is — a named value a widget shows, with key, label, format, unit, value and last-changed timestamp — which clearly separates it from siblings such as delete_metric or list_room_icons.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer you call this to see a room's metrics, and the mention of 'the per-room limit' hints at capacity checks before creating metrics, but neither the hint nor any when-not-to-use guidance is stated explicitly, and no alternatives are named.

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.

Resources