Skip to main content
Glama

anomalies_active

Retrieve currently active anomalies detected by trace-based and amount-based detectors, filtered by anomaly type, to investigate ongoing issues in observability data.

Instructions

Get currently active anomalies detected by trace-based and amount-based detectors.

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_active"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoAnomaly type to retrieveall

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.8.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden of behavioral disclosure. It implies a read of current state but says nothing about freshness, ordering, pagination, result size, or what an anomaly record actually contains.

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?

A single front-loaded sentence with no filler or redundancy. It is efficiently written, though its brevity leaves the rest of the definition thin.

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

Completeness3/5

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

For a one-parameter, fully documented read tool with no output schema, this is adequate but minimal. An agent still lacks any sense of result shape, volume, or how 'active' is determined.

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?

Schema coverage is 100% and the enum values are documented in the schema, so the baseline is 3. The description does add a little meaning by tying 'trace-based and amount-based' to the detector categories, but it does not explain what 'all' combines or the default behavior.

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 states a specific verb ('Get') and resource ('currently active anomalies'), and adds that they come from trace-based and amount-based detectors. It does not explicitly differentiate from the sibling anomalies_baselines, so it stops just short of a 5.

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 reference to alternatives such as anomalies_baselines. The agent must infer that 'currently active' means a live snapshot rather than historical baselines.

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