Skip to main content
Glama

authority_ranking

Read-onlyIdempotent

Ranks Hong Kong case results by court level and note-up data so you can prioritize authority and check later treatment before relying on a case.

Instructions

Rank case results by court level and note-up data.

live follows HK_LAW_LOCAL_ONLY. Not a citator of record; check later treatment before relying on a case.

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": {
      "query": "<query>"
    },
    "name": "authority_ranking"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoen
liveNo
courtNo
limitNo
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare this as a read-only, idempotent, open-world query, so the description does not need to restate safety. It does add genuinely new behavioral context: ranking is driven by court level and note-up data, results are not authoritative citator output, and the 'live' flag is governed by an environment setting (HK_LAW_LOCAL_ONLY) — though that environment variable reference is opaque without surrounding documentation.

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 sentences with the core action front-loaded and no filler; the caveat is placed where it matters most. Minor noise comes from the backtick formatting and an unexplained environment flag that the reader must already know.

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 five parameters, no output schema, and no schema descriptions, the definition should say more about what a ranked result looks like and how 'court' or 'limit' shape it. It covers the critical trust caveat well, but an agent still has to guess at result structure and most parameter behavior.

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% across five parameters, so the description carries the full burden and only partially meets it: it clarifies the meaning of the ranking inputs (court level, note-up data) and gives some semantic context for 'live'. The query, limit, and lang parameters receive no meaning beyond their names, leaving several gaps unaddressed.

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 ('Rank case results') and names the ranking criteria (court level and note-up data), which is enough to distinguish it from lookups like get_case. It stops short of naming a sibling such as note_up or search_cases as the alternative, so the boundary is inferred rather than stated.

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 caveat 'Not a citator of record; check later treatment before relying on a case' implicitly points the agent toward a citation-checking/note-up tool for authoritative treatment, which is useful implied guidance. There is no explicit statement of when to choose this over search_cases or note_up, and no preconditions are spelled out.

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