Skip to main content
Glama

semantic_status

Read-onlyIdempotent

Reports whether the semantic atlas is available and what it covers for Hong Kong criminal-law research.

Instructions

Report whether the semantic atlas is available and what it covers.

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_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A3.6/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 and a closed-world scope, so the safety profile is fully covered elsewhere. The description adds that the tool reports availability and coverage, but leaves 'what it covers' undefined — no mention of counts, corpus scope, index freshness, or what an unavailable answer looks like.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence with zero filler, front-loading the purpose ('report whether the semantic atlas is available') before the secondary clause about coverage. Nothing to trim.

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 trivial no-param, no-output-schema tool this is nearly adequate, but with no output schema the description is the only place to indicate what the response looks like (e.g. a boolean plus a coverage summary), and 'what it covers' is too vague to tell an agent what to expect.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter meaning for the description to supply; the baseline for a no-argument tool applies. Nothing misleading is stated about inputs.

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?

Specific verb ('Report') plus specific resource ('the semantic atlas'), and the two attributes reported (availability, coverage) are named. It separates itself from corpus_status/doj_status/sync_status only by the resource name 'semantic atlas', not by an explicit statement of difference.

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?

No explicit when-to-use or when-not-to-use statement. Usage is only implied — an agent can infer it is a pre-flight check for the semantic_* family (semantic_search, semantic_locate, semantic_cluster), but the description never says so or names any alternative.

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