Skip to main content
Glama

Get Metrics

tm_operation_get_metrics
Read-onlyIdempotent

Get metrics (tm_operations). Operation lifecycle and session management.

Instructions

Get metrics (tm_operations). Operation lifecycle and session management.

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

Input Schema

NameRequiredDescriptionDefault
confirmNoConfirm a destructive action (cancel) without elicitation.
detailsNoAdditional details (start).
total_stepsNoTotal steps (start).
operation_idNoOperation ID (get_progress/cancel/get_metrics).
operation_typeNoType of operation (start).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.4.7
    • addedInput schema / properties / confirm
      Added value: +{
      +  "default": false,
      +  "description": "Confirm a destructive action (cancel) without elicitation.",
      +  "type": "boolean"
      +}
  2. Addedv3.3.1

TDQS

C2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is fully covered by structured data. The description adds nothing beyond that, and notably does not explain why a read-only metrics tool exposes a "confirm" flag for a destructive cancel action or start-related fields — behavior an agent would otherwise trip over.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but both fragments are filler: the first duplicates the name and title verbatim, and the second is an uninformative taxonomy label. No useful content is front-loaded, so brevity here is under-specification rather than conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return shape need not be described, but the definition still omits what is measured (timing, step counts, success/failure, session totals) and at what granularity. For a tool with five mostly-unrelated parameters and nested object input, this leaves the agent guessing about invocation semantics.

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

Parameters2/5

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

Schema coverage is 100%, which sets a baseline of 3, but the schema is actively confusing: four of the five parameters belong to start/cancel operations (operation_type, total_steps, details, confirm) rather than to a metrics read. The description does not clarify which parameters are relevant here or that operation_id is optional and presumably scopes to a single operation, so it fails to resolve the ambiguity the schema creates.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Get metrics" merely restates the tool name and title; the parenthetical "(tm_operations)" restates the namespace prefix. The second sentence, "Operation lifecycle and session management," is a domain tag rather than a statement of what metrics are returned, so an agent cannot distinguish this from tm_operation_get_progress or tm_operation_list_sessions.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusions, and no pointer to the obvious siblings (get_progress, list_sessions, get_metrics). The agent must infer from the name alone that this is the aggregate-metrics view rather than a per-operation progress check.

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