Skip to main content
Glama

verify_citation

Read-onlyIdempotent

Verify Hong Kong criminal-law citations such as statutes and case numbers against the indexed corpus, confirming whether a cited authority exists before you rely on it.

Instructions

Verify a citation against the corpus.

live follows HK_LAW_LOCAL_ONLY; the public default is local. Examples: "Cap. 221 s.9J", "section 9J of Cap. 221", "[2021] HKCFA 1".

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

Input Schema

NameRequiredDescriptionDefault
langNoen
liveNo
citationYes

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: -trueNew value: +null
    • removedInput schema / properties / live / type
      Removed value: -"boolean"
  2. 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, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuine context beyond them by revealing that `live` is environment-variable governed and defaults to local. It stops short of explaining what changes behaviorally when live lookup is enabled (external calls, latency, differing results).

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, purpose front-loaded, with the env-var rule before the format examples. The reStructuredText double-backtick markup is noise in a tool description but does not impede comprehension.

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?

There is no output schema, so the description should say what a verification returns: a verdict, a matched provision, a confidence signal, or an error for unresolvable citations. None of that is present, and the relationship to verify_citations is unaddressed, which leaves real gaps for a three-parameter tool.

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 coverage is 0%, so the description must carry the full burden. It does well on `citation` by giving three accepted forms, and it partly explains `live` by tying it to HK_LAW_LOCAL_ONLY with a local public default. However, it never says what a live vs local verification actually does, and `lang` (presumably en/zh) is left completely 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: verify a citation against the corpus. That is clear enough to act on, but it never distinguishes this tool from the sibling verify_citations (plural), leaving the agent to guess which of the two near-identical names to call.

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 guidance on when to use this tool versus verify_citations or the get_* / search_* siblings, and no preconditions are stated. The citation-format examples help the agent format input, but they do not answer the selection question.

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