Skip to main content
Glama

anomalies_baselines

Retrieves current span duration baselines (mean, stdDev, p50, p95, p99 per operation) to support anomaly detection.

Instructions

Get current span duration baselines used for anomaly detection — mean, stdDev, p50, p95, p99 per operation.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.8.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral weight; it does identify this as a read ('Get') and enumerates the returned statistics (mean, stdDev, p50, p95, p99 per operation). It does not disclose how fresh the baselines are, how often they are recomputed, or whether the set covers all operations — meaningful gaps for a detection-support tool.

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?

A single front-loaded sentence that names the resource and then immediately lists the returned fields. No filler, no redundancy.

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 zero-parameter read with no output schema, the description usefully conveys what comes back (the percentile/statistic set and the per-operation granularity). What remains unclear is scope and freshness — whether these baselines span all operations and over what window they are computed.

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?

The tool takes zero parameters, so the baseline score of 4 applies; there is nothing for the description to disambiguate. The schema and description are consistent in implying an unfiltered fetch.

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

Purpose4/5

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

The description uses a specific verb+resource ('Get current span duration baselines') and qualifies the domain ('used for anomaly detection'), which an agent can distinguish from siblings like anomalies_active. It stops short of explicitly naming the related anomaly-listing tool, so the differentiation is implied rather than stated.

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?

The phrase 'used for anomaly detection' hints at the context in which baselines matter, but there is no explicit guidance on when to call this versus anomalies_active or traces_operations, and no stated prerequisites. Usage is inferable but not spelled out.

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