Skip to main content
Glama

BRAINIAC Predictive & Customer Analytics

DBSCAN density clustering with noise labels

predictive-analytics_dbscan-cluster
Read-onlyIdempotent

Density-based clustering with Euclidean or haversine distance, core/border/noise labelling, and an optional k-distance knee suggestion for eps. Price $0.04 USDC. POST /api/v1/predictive-analytics/dbscan-cluster. An unpaid call returns the x402 payment terms and does not run.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "columns": "<columns>",
      "rows": "<rows>",
      "eps": "<eps>"
    },
    "name": "predictive-analytics_dbscan-cluster"
  }
}

Input Schema

NameRequiredDescriptionDefault
epsYeseps, number. Required.
rowsYesrows, array. Required.
metricNometric, string, one of euclidean, haversine. Required.euclidean
columnsYescolumns, array. Required.
kDistanceNokDistance, boolean. Required.
minSamplesNominSamples, integer, from 2 to 1000. Required.

Output Schema

NameRequiredDescriptionDefault
capsNocaps. Object.
noiseNonoise. Number.
labelsNolabels. Array.
sourcesNosources. Array.
clustersNoclusters. Number.
rowsUsedNorowsUsed. Number.
kDistanceNokDistance. Null.
corePointsNocorePoints. Number.
droppedRowsNodroppedRows. Number.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior. Beyond that, the description adds important operational context: the endpoint, the $0.04 USDC price, and that an unpaid call returns x402 payment terms without running the clustering.

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?

The description is front-loaded with the core operation and then adds payment and endpoint details compactly. Every sentence carries useful information for selecting or invoking the tool.

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

Completeness4/5

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

Given that an output schema exists and the input schema is fully described, the description covers the key missing behavioral details: payment gating and clustering output semantics. It is largely complete, though explicit sibling-selection guidance would improve it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description adds meaningful semantics beyond the schema by clarifying that metric supports Euclidean or haversine distance and that kDistance provides an optional knee suggestion for eps, though it does not explain minSamples or row/column expectations.

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 states a specific method and resource: density-based clustering with Euclidean or haversine distance, core/border/noise labelling, and optional k-distance knee suggestion for eps. This clearly distinguishes it from centroid-based siblings such as kmeans-cluster.

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 density-based nature implies when it is appropriate, but the description does not explicitly say when to choose DBSCAN over kmeans or other siblings, nor when not to use it. Guidance is implied rather than stated.

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