Skip to main content
Glama

list_ordinances

Read-onlyIdempotent

Retrieve indexed Hong Kong ordinances and regulations, optionally filtered by title or Cap number, to identify relevant criminal-law statutes.

Instructions

List indexed ordinances/regulations, optionally filtered by title or Cap.

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

Input Schema

NameRequiredDescriptionDefault
langNoen
limitNo
queryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/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 openWorldHint=false. The description adds that results are indexed and may be filtered by title or Cap, but it does not cover pagination, return shape, or how the limit is applied, so it adds only modest behavioral context beyond the annotations.

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?

The description is a single front-loaded sentence with no wasted wording. It is appropriately brief for a list tool, though its terseness contributes to gaps handled under 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?

For a simple list tool with annotations covering safety, the description still leaves important gaps. With no output schema and 0% schema description coverage, it should clarify the query semantics and at least mention lang and limit behavior, but it does not.

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%, so the description must carry parameter meaning. It mentions filtering by title or Cap, which loosely maps to the query parameter, but it does not explain lang, limit, or the default limit of 200, leaving two of three 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 states a specific verb and resource: list indexed ordinances/regulations. It adds useful scope with 'optionally filtered by title or Cap,' but does not distinguish this tool from siblings such as search_legislation or list_section_versions.

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?

It describes what the tool can do but gives no explicit guidance on when to use it versus alternatives. There are no exclusions, prerequisites, or named sibling tools to route the agent.

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