Skip to main content
Glama
saidsurucu

Yargı MCP

by saidsurucu
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

search_bedesten_unified

Read-onlyIdempotent

Search Turkish court decisions from Yargıtay, Danıştay, local, appeals, and KYB courts using Boolean operators, with filters for court type, chamber, and date range. Returns 10 results per page.

Instructions

Use this for Turkish court decision records from Yargıtay, Danıştay, Local Courts, Appeals Courts, and KYB via Bedesten. Prefer narrow court_types over all courts. pageSize is intentionally fixed to 10 results per page. Bedesten is upstream rate-limited; avoid parallel repeated calls and wait retry_after seconds after 429 responses.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
phraseYesSearch query in Turkish. SUPPORTED OPERATORS: • Simple: "mülkiyet hakkı" (finds both words) • Exact phrase: ""mülkiyet hakkı"" (finds exact phrase) • Required term: "+mülkiyet hakkı" (must contain mülkiyet) • Exclude term: "mülkiyet -kira" (contains mülkiyet but not kira) • Boolean AND: "mülkiyet AND hak" (both terms required) • Boolean OR: "mülkiyet OR tapu" (either term acceptable) • Boolean NOT: "mülkiyet NOT satış" (contains mülkiyet but not satış) NOTE: Wildcards (*,?), regex patterns (/regex/), fuzzy search (~), and proximity search are NOT supported. For best results, use exact phrases with quotes for legal terms.
court_typesNoCourt types: YARGITAYKARARI, DANISTAYKARAR, YERELHUKUK, ISTINAFHUKUK, KYB
pageNumberNoPage number. Each page returns 10 results; pageSize is fixed by the server.
birimAdiNo Chamber filter (optional). Abbreviated values with Turkish names: • Yargıtay: H1-H23 (1-23. Hukuk Dairesi), C1-C23 (1-23. Ceza Dairesi), HGK (Hukuk Genel Kurulu), CGK (Ceza Genel Kurulu), BGK (Büyük Genel Kurulu), HBK (Hukuk Daireleri Başkanlar Kurulu), CBK (Ceza Daireleri Başkanlar Kurulu) • Danıştay: D1-D17 (1-17. Daire), DBGK (Büyük Gen.Kur.), IDDK (İdare Dava Daireleri Kurulu), VDDK (Vergi Dava Daireleri Kurulu), IBK (İçtihatları Birleştirme Kurulu), IIK (İdari İşler Kurulu), DBK (Başkanlar Kurulu), AYIM (Askeri Yüksek İdare Mahkemesi), AYIM1-3 (Askeri Yüksek İdare Mahkemesi 1-3. Daire) ALL
kararTarihiStartNoStart date (ISO 8601 format)
kararTarihiEndNoEnd date (ISO 8601 format)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

A4.5/5.0
Behavior5/5

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

Beyond annotations (readOnlyHint, idempotentHint, openWorldHint), the description adds behavioral traits: pageSize fixed to 10, upstream rate limiting, and the need to wait after 429 responses. No contradiction with annotations.

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 sentences, front-loaded with purpose and usage. Every sentence adds value: purpose, guidance, and behavioral notes. No wasted words.

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?

Given complexity (6 parameters, output schema exists, sibling tools for other domains), the description provides sufficient purpose, usage guidance, and behavioral context for correct tool selection and invocation.

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%, with detailed parameter descriptions (e.g., phrase operators, court_types enum). The description does not add parameter-level meaning beyond schema, so baseline 3 is appropriate.

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?

Description clearly states it is for Turkish court decision records from Yargıtay, Danıştay, Local Courts, Appeals Courts, and KYB via Bedesten. This specific scope distinguishes it from sibling tools like search_anayasa_unified or search_bddk_decisions.

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?

Description advises preferring narrow court_types over all courts and warns about rate limiting with specific instructions (avoid parallel repeated calls, wait retry_after). Provides clear context, though does not explicitly mention when not to use or list alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/saidsurucu/yargi-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server