Skip to main content
Glama

get_doj_document

Read-onlyIdempotent

Retrieve a Hong Kong DOJ publication by slug, selecting language, paragraph ranges, or a character limit for focused criminal-law research.

Instructions

Read a DOJ publication by slug, e.g. prosecution_ch5.

Args: slug: e.g. prosecution_ch5 or domesticviolence_11. lang: en or zh-Hant. paragraphs: Optional paragraph numbers/ranges, e.g. ["5.9"] or ["14-17"]. max_chars: Truncate the full text to this many characters.

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": {
      "slug": "<slug>"
    },
    "name": "get_doj_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoen
slugYes
max_charsNo
paragraphsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare this is a read-only, idempotent, closed-world, non-destructive operation, so the safety profile is covered. The description adds genuinely useful behavior not in the annotations: partial retrieval via paragraph ranges and truncation to max_chars. It does not disclose what happens on an unknown slug, whether paragraphs override max_chars, or whether truncation is silent.

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?

Front-loaded with a single-sentence purpose, then a compact Args block that is easy to scan. The per-parameter lines are justified because the schema itself has no descriptions, so there is little waste overall.

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?

With no output schema, the description should say more about what comes back — raw text versus structured sections, and how paragraph selection affects the result shape. It covers the input surface well and annotations cover safety, but the return-value side for a four-parameter retrieval tool remains unexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the burden and mostly does: it supplies slug examples, the actual allowed values for lang (en, zh-Hant) which the schema does not enumerate, paragraph syntax with range examples ("14-17"), and the meaning of max_chars. It falls short only on defaults and the interaction between paragraphs and max_chars.

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?

A specific verb and resource ("Read a DOJ publication by slug") with a concrete example of the identifier. It is clearly a retrieval tool, distinguishable from list_doj_documents or search_doj by the fact it takes a slug, though the description never names a sibling to draw the contrast explicitly.

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 when-to-use or when-not-to-use guidance, and no mention of alternatives such as list_doj_documents for discovering slugs, search_doj for unknown documents, or get_section for section-level access. Usage is only implied by the verb and the parameter shapes.

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