Skip to main content
Glama
Sign In
china-law-mcp

china-law-mcp

by THUboran
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_laws

Browse Chinese laws by name keyword or department to locate relevant statutes for legal research or citation verification.

Instructions

浏览库内法律目录（可按名称关键词或部门法筛选）。

Args: keyword: 法律名包含的关键词，如「劳动」「行政」。 department: 部门法，如「民法商法」「行政法」。 limit: 最多返回条数，默认 30。

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_laws"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
keywordNo
departmentNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. '浏览' implies a read-only operation and the limit default is stated, but there is no explicit confirmation of read-only behavior, side effects, or authentication needs.

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?

The purpose is front-loaded in one sentence, followed by a compact Args section. Every sentence adds useful information with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple list tool with an output schema, the description covers purpose and all parameters adequately. It does not explicitly state that no filters returns all laws up to the limit, nor any ordering or pagination behavior beyond the limit.

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 must compensate. It explains all three parameters with examples for keyword and department, and restates the limit default, adding clear meaning beyond the bare schema.

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?

The description states a specific verb and resource: browsing the law catalog, with optional filters by name keyword or department. It is clear what the tool does, but it does not differentiate itself from siblings like search_statutes or get_article.

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?

It implies usage for browsing/filtering laws, but gives no explicit when-to-use versus alternatives such as search_statutes. There are no exclusions or conditions for choosing this tool over its siblings.

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

Deploy Server

Other Tools