Skip to main content
Glama

list_section_versions

Read-onlyIdempotent

Retrieve all available historical version dates for a specified Hong Kong criminal-law section, helping track amendments and determine applicable statutory text.

Instructions

List all historical version dates available for a section.

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": {
      "cap": "<cap>",
      "section": "<section>"
    },
    "name": "list_section_versions"
  }
}

Input Schema

NameRequiredDescriptionDefault
capYes
langNoen
sectionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds that the result is a set of dates ('all historical version dates'), clarifying return scope beyond the annotations, but says nothing about ordering, date format, or what happens when no versions exist.

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 front-loaded sentence with zero filler; the resource and scope come first. Brevity here is a strength, though it leaves the gaps noted in other dimensions.

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?

With no output schema, 0% parameter coverage, and an undefined required parameter ('cap'), an agent lacks enough information to invoke this confidently. The description should at minimum explain what 'cap' and 'section' identify and what form the returned dates take.

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% across three parameters, so the description must compensate and mostly does not. 'Section' is loosely implied by the wording, but 'cap' and 'lang' are entirely unexplained, and 'cap' is an opaque name an agent cannot safely guess.

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 uses a specific verb+resource ('List all historical version dates available for a section'), so an agent knows it returns version metadata rather than section content. It does not differentiate itself from the nearby statute_history or get_section tools, which likely overlap in scope.

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?

There is no explicit when-to-use guidance, no prerequisites, and no mention of alternatives such as statute_history or get_section. The only hint is implicit: version dates would be listed before retrieving a specific version.

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