Skip to main content
Glama

get_section_range

Read-onlyIdempotent

Retrieve every section between two section numbers, inclusive, to read continuous statute ranges and handle numeric or letter suffixes in Hong Kong criminal legislation.

Instructions

Return all sections between two section numbers (inclusive).

Example: Cap. 221 sections 9A to 9J. Section ordering handles numeric and letter suffixes. Parts/Orders may restart numbering; read the part context.

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>",
      "start": "<start>",
      "end": "<end>"
    },
    "name": "get_section_range"
  }
}

Input Schema

NameRequiredDescriptionDefault
capYes
endYes
langNoen
limitNo
startYes
max_charsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile needs no restating. The description does add real domain behavior beyond that: ordering handles numeric and letter suffixes, and numbering can restart at Part/Order boundaries. However, it says nothing about how a limit default of 100 or max_chars truncation affects a request to 'return all' sections, which is a material omission for this operation.

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?

Two short paragraphs, front-loaded with the core behavior, followed by a concrete example. There is no filler or redundancy; the only mild weakness is that the closing caveat is stated without guidance on what an agent should actually do with it.

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 six parameters, zero schema descriptions, and no output schema, the description leaves too much unexplained: pagination, language selection, and character truncation are unaddressed. For a range-retrieval tool that can plausibly be truncated or paged, an agent cannot predict the response shape from this text.

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 six parameters, so the description must carry the semantic load. It clarifies start/end as inclusive section numbers and hints at cap format via the example, but lang, limit, and max_chars receive no mention at all, leaving half the parameters undocumented.

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 opens with a specific verb and resource: 'Return all sections between two section numbers (inclusive).' That is unambiguous about what the tool does and how it differs in shape from a single-section fetch, though it never names or contrasts with a sibling such as get_section.

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?

Usage is implied through the worked example ('Cap. 221 sections 9A to 9J') and the caveat that 'Parts/Orders may restart numbering; read the part context.' That is a useful precondition for interpreting results, but there is no explicit when-to-use versus when-to-use-a-sibling guidance.

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