Skip to main content
Glama

sync_doj

Idempotent

Update the local Hong Kong DOJ corpus by fetching curated Prosecution Code and domestic-violence policy pages, using conditional requests and checksums to avoid re-downloading unchanged content.

Instructions

Incrementally update the local DOJ corpus.

Fetches the curated Prosecution Code and domestic-violence policy pages (plus bounded discovery from their index pages), using conditional GETs and checksums. It is polite and may take 20–60 seconds. The full daily update is also available as hk-law sync-doj.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sync_doj"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoen
forceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A3.5/5.0
Behavior4/5

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

Beyond annotations, the description discloses the network mechanism (conditional GETs and checksums), the politeness/rate-limiting behavior, and the expected 20–60 second duration — all genuinely useful for an agent deciding whether to block on this call. It stops short of saying what happens to local data on a forced re-fetch or what a partial failure leaves behind.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with the action and scope, then runtime characteristics, then the CLI equivalent. Every sentence carries information an agent can act on; nothing is padded.

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?

For a network-touching, state-mutating sync with no output schema, the description covers scope, mechanism, and latency well, but leaves the two parameters unexplained and says nothing about the result of the sync (success/failure signal, what changed locally). Adequate but with clear gaps.

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% for two parameters (lang, force), and the description mentions neither. It does not explain that force presumably bypasses conditional GETs/checksums or what lang selects, so an agent must guess the effect of both inputs — a real gap given the low coverage.

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 ('Incrementally update the local DOJ corpus') and narrows scope to the Prosecution Code and domestic-violence policy pages plus bounded index discovery. It is clearly a sync/ingest operation rather than a query, so it is distinguishable in practice from siblings like doj_status or get_doj_document, though no sibling is named explicitly.

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 word 'Incrementally' and the mention of 'The full daily update is also available as hk-law sync-doj' imply a refresh workflow, but there is no explicit when-to-use guidance (e.g. run when doj_status shows staleness) or when-not-to-use/exclusion relative to verify_doj or doj_status. Usage is inferable rather than stated.

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