Skip to main content
Glama

semantic_cluster

Read-onlyIdempotent

Retrieve a semantic topic and representative member provisions from Hong Kong criminal-law data by cluster ID, with an optional limit, to inspect grouped legal content.

Instructions

Show one semantic topic and representative member provisions.

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": {
      "cluster_id": "<cluster_id>"
    },
    "name": "semantic_cluster"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
cluster_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds only that the result is a topic plus 'representative' member provisions — implying a sampled rather than exhaustive listing, which is useful but unexplained. With no output schema, it should say more about what is returned (e.g., whether limit truncates members).

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. It is efficient, though its brevity reflects under-specification rather than tightness against a rich schema.

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?

For a two-parameter lookup with no annotations on parameters and no output schema, the description should explain what a semantic cluster is, how to obtain cluster_id, and how limit shapes the response. None of that is present, leaving the agent to guess at the drill-down workflow.

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% and neither parameter is mentioned in the description. cluster_id is required and the description never says where a cluster id comes from (presumably semantic_clusters), and limit's default of 20 and its effect (members per cluster vs clusters) is undocumented in both places. The description does not compensate for the coverage gap.

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 concrete verb+resource: 'Show one semantic topic and representative member provisions.' The singular 'one semantic topic' implicitly contrasts with the plural sibling semantic_clusters, and 'representative member provisions' signals the return content. It stops short of naming the alternative explicitly, so it is clear but not fully differentiated.

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?

No guidance on when to use this vs semantic_clusters (list all clusters) or semantic_neighbors (related items). The agent must infer from the name alone that this is the drill-down call for a single cluster. No prerequisites or exclusions are stated.

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