Skip to main content
Glama

sentencing_research

Read-onlyIdempotent

Extracts penalty language from a Hong Kong statutory provision and finds related sentencing case leads for an offence, noting results are not a sentencing tariff.

Instructions

Return penalty text and sentencing case leads for an offence.

live_cases follows HK_LAW_LOCAL_ONLY. Not a sentencing tariff. Extracts penalty language from the provision and searches for sentencing material in the case corpus.

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

Input Schema

NameRequiredDescriptionDefault
capYes
langNoen
sectionYes
case_limitNo
live_casesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.3.0
    • addedInput schema / properties / live_cases / anyOf
      Added value: +[
      +  {
      +    "type": "boolean"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / live_cases / default
      Previous value: -falseNew value: +null
    • removedInput schema / properties / live_cases / type
      Removed value: -"boolean"
  2. First observedv0.2.0

TDQS

B3.4/5.0
Behavior4/5

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

Beyond the annotations, the description discloses the live_cases policy constraint, clarifies that the output is not a sentencing tariff, and explains the extraction-plus-search method. It does not cover authentication or rate limits, but the annotations already handle the safety profile.

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 short and front-loads the purpose. The final sentence restates the method already implied by the first, but no sentence is seriously wasteful and the limitations are easy to locate.

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 and 0% schema description coverage, the description is incomplete for a five-parameter research tool: it does not explain most parameters or the return shape. It does give enough to understand the tool's broad intent and one parameter policy.

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 explain all five parameters. It only partially addresses live_cases (referencing HK_LAW_LOCAL_ONLY) and says nothing about cap, section, lang, or case_limit.

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 resources: 'Return penalty text and sentencing case leads for an offence.' This clearly distinguishes sentencing research from generic case or statute lookup, though it does not explicitly name sibling tools it replaces.

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?

The description says 'Not a sentencing tariff' and notes that live_cases follows HK_LAW_LOCAL_ONLY, giving some boundary guidance. However, it does not say when to use this tool versus search_cases or doctrine_research, leaving alternative selection implicit.

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