Skip to main content
Glama

compute_clusters

Computes live connected-components vector clusters for SubatomicParticles or QuantumStates across particle groups without changing the database, helping find similar physics entities.

Instructions

Compute live connected-components vector clusters for SubatomicParticles or QuantumStates across particle groups without modifying the database.

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

Input Schema

NameRequiredDescriptionDefault
forceNoBypass Rails memory cache and recalculate adjacency graph
levelNoSimilarity granularity level from 1 (tight multiplet analogs, <= 0.16 cosine dist) to 15 (full catalog coverage absorption, <= 0.30)
target_typeNoTarget entity class to cluster: SubatomicParticle or QuantumStateSubatomicParticle
full_coverageNoForces 100% catalog assignment / zero singletons via nearest-cluster absorption

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry behavioral disclosure, and it does convey two useful traits: results are computed live rather than stored, and nothing is written to the database. It says nothing about cost/latency of a full-graph recompute, caching implications, or whether results are ephemeral.

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?

A single dense sentence with the action front-loaded and no filler. It is appropriately sized, though it spends its length on scope rather than on return behavior.

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

Completeness3/5

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

There is no output schema and no annotations, so the description is the only place an agent could learn what the returned clusters look like (member lists, labels, singleton handling) — and it does not. The mutation-free guarantee is covered, but return shape and the meaning of a live computation are left implicit.

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%, so force, level, target_type, and full_coverage are fully documented in the schema and a baseline of 3 applies. The description adds no parameter meaning of its own — even the cache-related 'force' flag is only obliquely echoed by the word "live."

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: "Compute live connected-components vector clusters" over named entity types (SubatomicParticles, QuantumStates) and across particle groups. That scope, plus "without modifying the database," distinguishes it from the persistence-oriented siblings such as create_cluster_snapshot and create_cluster_report, though no sibling is named explicitly.

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 phrase "without modifying the database" implicitly tells the agent this is the non-persisting option versus the create_cluster_* tools, but it never states when to choose this over a snapshot or report, nor any prerequisites. Usage is inferable rather than guided.

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