Skip to main content
Glama

compute_clusters

Computes live connected-component vector clusters for Species or Organism entities across biomes without altering the database, with adjustable similarity levels and optional full catalog coverage.

Instructions

Compute live connected-components vector clusters for Species or Organisms across biomes 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 functional analogs, <= 0.16 cosine dist) to 15 (full catalog coverage absorption, <= 0.30)
target_typeNoTarget entity class to cluster: Species or OrganismSpecies
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?

With no annotations supplied, the description carries the full disclosure burden, and it does deliver the most important trait: the operation does not modify the database and is computed live. It says nothing about cost/latency, whether results are cached (only the schema's `force` hints at this), or whether output is persisted anywhere.

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 well-formed sentence with the key qualifier ('without modifying the database') placed at the end for emphasis. No filler, no repetition of the name. It could be marginally tighter but wastes nothing.

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?

For a four-parameter compute tool with no output schema and no annotations, the description covers the safety profile but omits what the returned cluster data looks like in shape or size, and how expensive a recompute with `force` is. Adequate to invoke, not complete.

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 each of the four parameters documented in-schema including level ranges, defaults, and the meaning of `force` and `full_coverage`. The description adds no parameter-level meaning beyond that, so the baseline of 3 applies.

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?

The description names a specific verb ('Compute') and a specific resource ('live connected-components vector clusters'), scoped to 'Species or Organisms across biomes'. That is enough to distinguish it from sibling tools that only list, get, or snapshot cluster data, though it does not name any of them 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 'live ... without modifying the database' implies this is the on-the-fly computation path rather than the persisted snapshot/report tools, so usage is inferable. However, there is no explicit statement of when to prefer this over create_cluster_snapshot or list_cluster_groups, and no exclusions or prerequisites.

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