Skip to main content
Glama

verify_citations

Read-onlyIdempotent

Extracts and verifies every citation in a passage against Hong Kong criminal-law sources, making reference accuracy clear and traceable.

Instructions

Extract and verify every citation in a passage.

live follows HK_LAW_LOCAL_ONLY; the public default is local.

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": {
      "text": "<text>"
    },
    "name": "verify_citations"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoen
liveNo
textYes

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

C2.9/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 safety is covered. The description adds that `live` is governed by HK_LAW_LOCAL_ONLY and that the public default is local, which is genuinely useful behavioral context, but it never explains the consequence of live=false (offline/cached verification? failure mode?), leaving the key behavior opaque.

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 purpose front-loaded and no redundant wording. However, the second sentence is cryptic—an unexplained backtick-quoted env var ('HK_LAW_LOCAL_ONLY') that reads as internal jargon rather than an agent-readable instruction.

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?

No output schema exists, so the description should explain what verification results look like (per-citation status, resolved references, failures), and it does not. Combined with zero parameter documentation and an unexplained `live` toggle for a tool that reaches external/open-world sources, an agent cannot confidently call it or interpret results.

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 all three parameters, so the description must compensate and largely does not. It gestures at `live` via an environment-variable name but explains neither its values nor its effect, and says nothing about `text` (passage format/length) or `lang` (default 'en' implies language of citations but that is never stated).

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 specific verb and resource: 'Extract and verify every citation in a passage.' The plural/'every ... in a passage' scope implicitly hints at batch handling versus the sibling verify_citation, but the description never names or contrasts that sibling, so differentiation is left to inference.

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 stated condition for choosing this tool over verify_citation, authority_ranking, or get_case, and no prerequisites or exclusions. The only guidance offered is about the `live` setting, not about when to invoke the tool.

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