Skip to main content
Glama

waveguard_scan

Detect anomalies in any data type by sending normal examples and suspect samples in one API call. Returns per-sample scores, confidence, and explanatory features using GPU-accelerated wave physics.

Instructions

Detect anomalies in data using GPU-accelerated wave physics simulation. Fully stateless — send training data (normal examples) and test data (samples to check) in ONE call. Returns per-sample anomaly scores, confidence levels, and the top features explaining WHY each anomaly was flagged. Works on any data type: JSON objects, numbers, text, time series, arrays. No separate training step required.

Example: to check if server metrics are anomalous, send 3-5 normal readings as training, and the suspect readings as test.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
trainingYes2+ examples of NORMAL/expected data. These define what 'normal' looks like. All samples should be the same type and shape. More samples = better baseline (4-10 is ideal).
testYes1+ data points to check for anomalies. Same type/shape as training data. Each sample is scored independently.
sensitivityNoAnomaly threshold multiplier (default: 2.0). Lower = more sensitive (flags more anomalies). Higher = less sensitive. Range: 0.5 to 5.0.
encoder_typeNoData encoder type. Omit to auto-detect from data shape. Auto-detection works well for most data.
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses statelessness, single-call usage, returns per-sample scores, confidence levels, and top features. Does not mention authorization or rate limits, but for a detection tool this is adequate.

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?

Description is two concise paragraphs: first states purpose and key features, second provides a clear example. No unnecessary words, and front-loaded.

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?

Given 4 parameters and no output schema, the description is complete: explains workflow, return values, and includes an example. No missing critical information.

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 description coverage is 100% with well-described parameters. The description adds overall context and example but does not significantly enhance parameter meanings beyond the schema. Baseline 3 is appropriate.

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?

Description clearly states 'Detect anomalies in data using GPU-accelerated wave physics simulation', specifying verb and resource. It distinguishes from sibling tools like waveguard_scan_timeseries by emphasizing it works on any data type and is the general-purpose version.

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

Usage Guidelines4/5

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

Explicitly describes stateless one-call operation and no separate training step, with an example. Does not explicitly state when not to use, but the mention of working on any data type implies the time-series sibling is for specialized cases.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/gpartin/WaveGuardClient'

If you have feedback or need assistance with the MCP directory API, please join our Discord server