Skip to main content
Glama

get_section

Read-onlyIdempotent

Retrieve a Hong Kong ordinance section or schedule with source provenance by Cap number and section, optionally in English or Traditional Chinese, for statute-based legal research.

Instructions

Return a Hong Kong ordinance section or schedule with provenance.

Args: cap: Cap number, e.g. "221" or "Cap. 221". section: Section number, e.g. "9J", "s9J", or "sch3". lang: "en" (default) or "zh-Hant". max_chars: Truncate very long sections/schedules to this many characters.

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

Input Schema

NameRequiredDescriptionDefault
capYes
langNoen
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 declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description still adds real behavior beyond them: results carry provenance, and long sections are truncated at max_chars, which explains a non-obvious output-shaping effect. "Provenance" itself is left undefined, which keeps this short of a 5.

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?

One front-loaded purpose sentence followed by a compact Args block; every line carries information and nothing is padded. The Args list is slightly redundant with the schema titles but earns its place by supplying format examples.

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?

With no output schema, the description should explain what a section record contains; "with provenance" is the only hint and is unexplained. For a simple read-only getter this is acceptable, but the truncated-vs-full return shape and the structure of provenance are left to discovery.

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

Parameters3/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 carry this burden; it does document all four parameters, including accepted input formats like "Cap. 221" or "s9J", "sch3", and the en/zh-Hant language choice. However the formats are only illustrated by example, and the defaults for lang and max_chars come from the schema rather than the prose, so the compensation is partial rather than complete.

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 specific verb and resource ("Return a Hong Kong ordinance section or schedule") plus a scope qualifier ("with provenance"), which distinguishes it from broad search tools. It does not, however, differentiate itself from the close sibling get_section_range, which a reader would need to infer.

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?

Contains no when-to-use or when-not-to-use guidance, no mention of alternatives such as get_section_range, list_section_versions or search_legislation, and no prerequisites. The only guidance is argument-format examples, which belong to parameter semantics rather than tool selection.

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