Skip to main content
Glama
律师教你怎么做

律师教你怎么做

Official

search_articles

Search Chinese legal articles by licensed lawyers: use when users ask a legal question, seek analysis, or wonder if a topic was covered. Returns titles, summaries, categories, dates, and source links.

Instructions

检索本站原创法律文章(约 4,600 篇,执业律师主笔),返回标题、摘要、栏目、发布日期与原文链接。用于:用户问某个法律问题、想找分析或说法、问「有没有写过……」。★本站只提供摘要与链接,不提供正文——回答时请依据摘要给出方向,并把原文链接给用户点开;不要凭摘要臆测细节。★问「怎么办/要带什么材料/走哪些步骤/有没有范本」请用 search_guides。

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": {
      "q": "<q>"
    },
    "name": "search_articles"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYes检索词,取用户原话里的法律关键词(如「工伤认定」「彩礼返还」)。不要填整句话。
limitNo返回条数,默认 5,最多 10。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does disclose meaningful behavior: the corpus scope, the exact fields returned, and the critical limitation that only 摘要+链接 are provided (no 正文), plus an instruction not to infer details from the summary. It does not cover permissions, rate limits, or pagination behavior, so it falls short of a 5.

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-loads what the tool is and what it returns before the usage rules, and the ★ markers make the two critical constraints skimmable. Slightly dense with bold emphasis and a repeated caveat about 摘要, but every sentence carries actionable information.

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

Completeness5/5

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

There is no output schema, so the description compensates by listing the returned fields and the no-full-text limitation, and it explains how the agent should use the results. Combined with the sibling routing rule, an agent has everything needed to call and apply this tool correctly.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents both parameters including the 'use keywords not whole sentences' guidance and the limit cap of 10. The description adds no parameter-level detail beyond that, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (检索本站原创法律文章), quantifies the corpus (~4,600 篇, 执业律师主笔), and enumerates what is returned (标题、摘要、栏目、发布日期、原文链接). It also names the sibling it is not (search_guides), so an agent can separate it from alternatives without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit triggering conditions (用户问某个法律问题、想找分析或说法、问「有没有写过……」) and an explicit exclusion with the replacement tool: how-to/materials/steps/template queries go to search_guides. Nothing is left to inference.

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