Skip to main content
Glama

case_graph

Read-onlyIdempotent

Retrieve outgoing cited cases and incoming note-up citations for a Hong Kong case citation, using a local cache by default or live note-up when enabled.

Instructions

Return outgoing cited cases and incoming note-up citations.

live_note_up follows HK_LAW_LOCAL_ONLY; the public default uses the local cache.

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": {
      "citation": "<citation>"
    },
    "name": "case_graph"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoen
citationYes
live_note_upNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.3.0
    • addedInput schema / properties / live_note_up / anyOf
      Added value: +[
      +  {
      +    "type": "boolean"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / live_note_up / default
      Previous value: -trueNew value: +null
    • removedInput schema / properties / live_note_up / type
      Removed value: -"boolean"
  2. 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 cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the description gets credit mainly for the HK_LAW_LOCAL_ONLY / local-cache note, which is real configuration context. However it is cryptic about what the null default actually resolves to and says nothing about latency or how the two citation directions are combined in the response.

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 compact sentences, front-loaded with the core return value before the configuration caveat. No filler, though the escaped backticks/quotes read as raw markup rather than deliberate formatting.

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?

A read-only graph tool with no output schema and no parameter documentation leaves the agent guessing at the return shape (edge lists? case objects? direction labels?) and at input formatting. For a 3-parameter tool at 0% coverage, the description does too little.

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 three parameters, so the description must carry the load, but it only gestures at live_note_up and never explains 'citation' format (neutral citation vs reporter) or what 'lang' controls. Two of three parameters remain undocumented anywhere.

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 concrete verb and result: returns 'outgoing cited cases and incoming note-up citations', i.e. a citation graph for one case. This is specific enough to separate it from get_case or note_up, though the term 'note-up' assumes domain familiarity.

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?

There is no statement of when to call this rather than note_up, get_case, or verify_citation, and no prerequisites such as needing a resolved citation string. Only the live_note_up behaviour is addressed.

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