Skip to main content
Glama

semantic_clusters

Read-onlyIdempotent

Lists semantic-atlas topics for Hong Kong criminal-law research, with optional filtering by label or Cap. title to locate relevant statute clusters.

Instructions

List semantic-atlas topics, optionally filtered by label or Cap. title.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

C2.7/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is fully covered. The description adds only that filtering is optional; it says nothing about result volume, whether the limit of 50 is a page size or a hard cap, or how matching is performed.

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 front-loaded sentence with no filler or repetition. It is efficient, though its brevity contributes to the specification gaps noted in other dimensions rather than being a model of completeness.

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?

This is a simple two-parameter read tool with annotations, but it has no output schema, so the description should explain what a returned "topic" contains and how pagination interacts with limit. It leaves both unaddressed and uses the unexplained abbreviation "Cap. title", which an agent cannot reliably interpret.

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%, so the description carries full responsibility for parameter meaning. It partially clarifies that query filters by "label or Cap. title", but the limit parameter is never mentioned and no matching semantics (exact vs substring) are described.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb+resource pattern ("List semantic-atlas topics") is present, so the general action is identifiable. However, "semantic-atlas topics" is unexplained jargon and the description does nothing to separate this listing tool from siblings like semantic_search, semantic_neighbors, or semantic_cluster, so the agent must guess at the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description states that filtering is optional via "label or Cap. title", which hints at when the query parameter is relevant, but it never says when to choose this tool over the semantic_* siblings or what happens if no filter is supplied. No exclusions or alternatives are given.

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