Skip to main content
Glama

SmartHukuk Legal Research

Resmî kaynaklarda emsal karar ara

search_public_precedents
Read-only

E-posta ile etkinleştirilmiş trialToken kullanarak doğal dil, esas/karar numarası veya hukuki konu ile public resmî karar kaynaklarında arama yapar. İlk 5 başarılı arama ücretsizdir. Sonuçlar künye ve resmî kaynak URL’si içerir; hukuki görüş üretmez.

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

Input Schema

NameRequiredDescriptionDefault
limitNoDöndürülecek sonuç sayısı (1-5)
queryYesKişisel veri içermeyen hukuki konu, olay özeti veya karar künyesi
dateToNoİsteğe bağlı bitiş tarihi, YYYY-MM-DD
chamberNoİsteğe bağlı daire/kurul filtresi
dateFromNoİsteğe bağlı başlangıç tarihi, YYYY-MM-DD
trialTokenNostart_mcp_precedent_trial aracından dönen gizli deneme tokenı

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is covered. The description adds value beyond that: token-based auth via email activation, a 5-search free quota, what results contain (bibliographic record plus official source URL), and an explicit disclaimer that no legal opinion is produced.

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?

Three tight sentences with zero filler: search behavior first, then access/quota, then output contract and scope limit. Every sentence carries information an agent needs.

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 six-parameter tool with no output schema, the description covers auth requirements, quota, and the shape of results, which is what an agent needs before calling. Minor gaps remain around paging beyond the 1-5 limit and what an empty result looks like, but nothing essential is missing.

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 all six parameters are already documented in the schema, including limit, date range, chamber, and trialToken. The description only loosely characterizes what the query accepts; with the schema doing the heavy lifting, the baseline 3 is appropriate.

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+resource: searching public official decision sources, and names the three query modes (natural language, case/decision number, legal topic). It does not explicitly distinguish itself from the sibling find_public_legal_resource, so sibling differentiation is left to inference.

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

Usage Guidelines4/5

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

It gives a concrete prerequisite and context: the trialToken must be activated by email and obtained from start_mcp_precedent_trial, and the first 5 successful searches are free. It offers no explicit when-not-to-use guidance or named alternatives beyond that token dependency.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources