Skip to main content
Glama
Sign In

KrystalView Analytics

by io.github.KrystalView
OverviewDiscussionsAdmin

Get Anomalies

get_anomalies
Read-onlyIdempotent

List detected traffic, friction, bounce, and conversion anomalies for the site.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results to return.
unacknowledged_onlyNoOnly include unacknowledged anomalies.

Output Schema

NameRequiredDescriptionDefault
dataYesDetected traffic, bounce, friction, and conversion anomalies for the site.
metaYesSite and rate-limit metadata for the current MCP call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the description adds value by specifying the types of anomalies returned (traffic, friction, bounce, conversion). No contradictory information.

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, focused sentence that is immediately actionable and contains no extraneous information.

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 the presence of an output schema and fully described parameters in the schema, the description is complete. It conveys the essential purpose without needing to repeat structured details.

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 both parameters (limit, unacknowledged_only) already described in the schema. The tool description does not add any additional parameter semantics beyond the schema.

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?

The description clearly states it 'List[s] detected traffic, friction, bounce, and conversion anomalies for the site,' specifying both the verb and the resource types, and it distinguishes from sibling tools like get_errors.

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?

No explicit guidance is provided on when to use this tool versus alternatives like get_errors or get_notifications. The usage is implied but lacks exclusions or context.

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

All KrystalView Analytics toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources