Skip to main content
Glama

BRAINIAC Data Quality Intelligence

Detect statistical outliers

data-quality_csv-outlier-detect

Flag numeric values outside a Tukey fence of 1.5 times the interquartile range when a column has at least eight numbers. Each flag is a possible outlier, not a confirmed error. Price $0.05 USDC. POST /api/v1/data-quality/csv-outlier-detect. Unpaid calls return 402 and do not run.

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": "data-quality_csv-outlier-detect"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
fileNo
jsonNo
recordsNo
keyColumnsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the minimum sample size (eight numbers), the interpretive limit of the output (possible outlier, not confirmed error), the price ($0.05 USDC), the 402 behavior for unpaid calls, and that unpaid calls do not execute. What it omits is any statement of what the input must contain for execution to succeed.

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?

Four short sentences, front-loaded with the method and sample-size condition, then cost and payment semantics. Every sentence carries information; the endpoint URL is mildly infrastructural but still useful for backend routing. No filler.

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?

Despite the rich behavioral disclosure, the definition is incomplete for a tool with five undocumented input parameters, mutual-exclusivity questions (csv vs file vs json vs records), a nested file object, and no output schema. The agent cannot tell from the description how to construct a valid call or what the returned flags look like structurally.

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% across five parameters, including a nested file object and a records array, yet the description names none of them. It never indicates whether the agent should supply the csv string, the file object, the json string, or records, nor what keyColumns does. With such high schema opacity, this is a real gap that should have been compensated for.

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 plus the exact method: flag numeric values outside a Tukey fence of 1.5x IQR. An agent knows immediately what the tool computes. It does not differentiate from the sibling data-quality tools by name, but the analytical purpose is unambiguous.

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 description implies when the tool applies by requiring at least eight numbers in a column, and it cautions that flags are possible outliers rather than confirmed errors. There is no explicit when-to-use or when-not-to-use guidance relative to the sibling audit/detect tools, and no mention of prerequisites for input shape.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources