Skip to main content
Glama
adpilot-mcp

adpilot-mcp

Official
by sholaxai

detect_anomalies

Read-only

Flag unusual spend, CPA, ROAS, CTR, or CPC changes against a trailing baseline using robust z-scores, returning severe issues first for campaign review.

Instructions

Flag unusual moves in spend/CPA/ROAS/CTR/CPC using robust z-scores (median + MAD) against a trailing baseline. Returns the most severe first.

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

Input Schema

NameRequiredDescriptionDefault
daysNo
thresholdNo
onlyHarmfulNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3/5.0
Behavior3/5

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

readOnlyHint=true already covers the safety profile, and the description adds real value by disclosing the statistical method (median + MAD robust z-scores against a trailing baseline) and the result ordering ('most severe first'). It omits behavior the annotations do not cover: that results are filtered to harmful anomalies by default, and how far back the baseline reaches.

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?

Two tightly written sentences with zero filler; the detection target is front-loaded and the output ordering follows immediately. Every clause carries information.

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?

For a read-only analysis tool with three undocumented parameters and no output schema, the description should at minimum explain the defaults that change results. The undisclosed onlyHarmful=true default materially alters what the agent sees, and threshold semantics are absent entirely.

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 description coverage is 0%, so the description carries the full burden for days, threshold, and onlyHarmful — and it explains none of them. 'Trailing baseline' only loosely hints at the days window, and the consequential onlyHarmful=true default, which silently narrows results, is never mentioned.

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?

States a specific verb and resource ('Flag unusual moves in spend/CPA/ROAS/CTR/CPC') and names the detection method, so an agent can tell this apart from performance-listing siblings. It does not explicitly reference any sibling tool, which keeps it 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 or when-not-to-use guidance and no mention of alternatives such as campaign_performance for raw metric inspection. Usage is only inferable from the verb 'Flag', so the agent must guess whether to call this before or instead of the reporting tools.

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