Skip to main content
Glama

list_doj_documents

Read-onlyIdempotent

List indexed DOJ publications and paragraph counts, with language and category filters, to locate relevant Hong Kong criminal-law source documents.

Instructions

List indexed DOJ publications and their paragraph counts.

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

Input Schema

NameRequiredDescriptionDefault
langNoen
limitNo
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare the safe read-only, idempotent, closed-world profile, so the safety burden is covered. The description adds two useful behavioral facts beyond that: results are limited to already-indexed documents (unsynced material will not appear) and each entry carries a paragraph count. It says nothing about the default 200-item cap or truncation behavior.

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?

One front-loaded sentence with no filler and no repetition of the tool name. It is efficient but arguably under-sized for a three-parameter listing tool, so not a 5.

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?

For a listing tool with three optional filters, no output schema, and zero parameter documentation, the description is too thin. An agent cannot tell what category values are valid, whether results are paginated, or how the limit interacts with the paragraph-count payload.

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 (lang, limit, category), and the description never mentions filtering, language selection, or the result limit. Parameter names and defaults in the schema are self-explanatory enough to keep this above the floor, but the description contributes nothing to disambiguate category semantics or the effect of limit.

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 (List) and a specific resource (indexed DOJ publications), plus a return-content detail (paragraph counts). It reads clearly against siblings like get_doj_document and search_doj, though it never explicitly names what distinguishes it from them.

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 instead of search_doj or get_doj_document, no prerequisites, and no exclusions. The agent must infer from the tool name alone that this is a browse/enumerate step rather than a lookup or sync.

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