Skip to main content
Glama

search_doj

Read-onlyIdempotent

Search Hong Kong DOJ prosecution policy materials, including the Prosecution Code and domestic-violence policy, to find relevant paragraphs and then read the full page before relying on them.

Instructions

Search the DOJ Prosecution Code and prosecution policies.

The local DOJ corpus covers the Prosecution Code and the domestic-violence prosecution policy. category is prosecution_code or domestic_violence. This is policy material, not legislation; read the full page before relying on a paragraph.

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": {
      "query": "<query>"
    },
    "name": "search_doj"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoen
limitNo
queryYes
categoryNo
max_charsNo
include_textNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so safety is covered. The description adds real value by bounding the corpus and warning that paragraph-level reliance is unsafe. It does not explain limit, max_chars, or how include_text changes the response, which matters for a search tool with no output schema.

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?

Short, front-loaded with purpose, then corpus scope, then category values, then a caveat. Every sentence carries information, with only minor redundancy between the first line and the corpus sentence.

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 search tool with no output schema and six undocumented parameters, the description covers what the corpus contains and how to filter by category but leaves result shape, paging via limit, and text-inclusion behavior unexplained. Adequate for intent, thin for correct invocation.

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%, so the description must carry parameter meaning, and it only explains one of six: category with its two allowed values. Query, lang, limit, max_chars and include_text are left entirely undefined, including the non-obvious include_text default of false.

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?

Opens with a specific verb and resource ("Search the DOJ Prosecution Code and prosecution policies") and scopes the corpus to two named categories. It also distinguishes itself from legislation-focused siblings by stating "this is policy material, not legislation," though it never names a sibling tool directly.

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?

Usage context is implied by the corpus scope and category values, and the caution to read the full page before relying on a paragraph is a useful guardrail. However, it never says when to choose this over search_legislation, semantic_search, or get_doj_document, so an agent must infer the routing.

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