Skip to main content
Glama

semantic_locate

Read-onlyIdempotent

Locate a legislation citation's point and cluster in the semantic atlas to map where the citation fits in Hong Kong criminal-law research.

Instructions

Find a legislation citation's point(s) and cluster in the semantic atlas.

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": {
      "citation": "<citation>"
    },
    "name": "semantic_locate"
  }
}

Input Schema

NameRequiredDescriptionDefault
citationYes
languageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's burden is to add context — but it adds none about lookup failures for unknown citations, whether the atlas lookup is approximate, or what the response contains. "Semantic atlas" is never explained, so the agent cannot anticipate the behavior of the lookup itself.

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, but the compression comes at the cost of clarity around "point(s)" and "cluster".

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?

No output schema and zero parameter documentation mean the description carries the full explanatory load, yet it never says what a "point" or "cluster" result is, how many are returned, or what language does. For a semantic-resolution tool with an unusual return shape, this is a significant gap.

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 must compensate: it only implies that the citation parameter is a legislation citation. The optional "language" parameter (default null) — presumably affecting which atlas/cluster is matched — is entirely unexplained, which matters for a semantic lookup.

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?

Uses a specific verb ("Find") and names the resource (a legislation citation's points and cluster in the semantic atlas), which places it in the semantic_* family. However, "point(s)" and "cluster" are undefined domain jargon, so an agent cannot fully picture what is returned or how it differs from semantic_cluster or semantic_neighbors.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as semantic_cluster, semantic_neighbors, or semantic_search. The agent must infer from the name alone whether to call this before or instead of those siblings.

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