Skip to main content
Glama

statute_history

Read-onlyIdempotent

Retrieve a Hong Kong criminal-law provision's text in force on a specified YYYY-MM-DD date, with a warning if historical archives are unavailable and current text is returned.

Instructions

Return the provision text in force on a date (YYYY-MM-DD).

Uses the official DATA.GOV.HK Past Version archives if ingested. If the historical corpus is unavailable, returns the current text with historical: false and an explicit warning.

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

Input Schema

NameRequiredDescriptionDefault
capYes
langNoen
as_ofNo
sectionYes
max_charsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world semantics, so the description is not obligated to restate safety. It adds genuinely non-obvious behavior instead: the upstream source (DATA.GOV.HK Past Version archives) and the degraded-mode fallback that returns current text with historical: false plus a warning. The only gap is that 'if ingested' is undefined for the caller.

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?

Three short sentences, front-loaded with the core behavior, with the fallback caveat immediately after. Nothing is padded, though the 'if ingested' phrasing is vague enough to cost a little precision.

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?

There is no output schema, and the description does disclose one return field (historical: false) and a warning path, which is more than most. But for a 5-parameter tool with zero schema documentation, the unaddressed cap/section/lang/max_chars parameters and the undefined ingestion precondition leave the definition short of complete.

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 5 parameters, so the description must compensate and largely does not. It explains as_of indirectly via 'in force on a date' and its format, but cap, section, lang, and max_chars (which likely controls truncation of the returned provision text) get no mention at all.

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 states a specific verb and resource with an explicit temporal qualifier: 'Return the provision text in force on a date'. That distinguishes it in spirit from current-text siblings like get_section, but it never names those siblings, so the differentiation is left implicit.

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?

It gives the date format (YYYY-MM-DD) and describes the fallback path, which is real usage context. However, it never says when to prefer this over list_section_versions or get_section, nor what preconditions ('if ingested') the caller should check first, so the when-to-use decision is only implied.

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