Skip to main content
Glama
saidsurucu

Mevzuat MCP

by saidsurucu

search_mevzuat

Search Turkish legislation from the Ministry of Justice database by title, keyword, law number, or browse by type. Filter by official gazette date or legislation type to locate specific statutes.

Instructions

Search or browse all Turkish legislation on bedesten.adalet.gov.tr.

Covers 12 legislation types: Kanunlar, Cumhurbaşkanı Kararnameleri, Bakanlar Kurulu Yönetmelikleri, CB Yönetmelikleri, CB Kararları, CB Genelgeleri, KHK'lar, Tüzükler, Kurum/Kuruluş Yönetmelikleri, Üniversite Yönetmelikleri, Tebliğler, Mülga Mevzuat.

Search modes:

  • mevzuat_adi: Title/keyword search (recommended, searches legislation name)

  • phrase: Full-text content search (Solr syntax, searches inside document body)

  • mevzuat_no: Direct number lookup (e.g., '5237' for TCK)

  • Browse: Leave all empty to list by type

Date range filtering:

  • Use resmi_gazete_tarihi_start and/or resmi_gazete_tarihi_end (DD/MM/YYYY)

  • Single date: set both start and end to the same date

  • Year range: '01/01/2024' to '31/12/2024'

Workflow: Use this tool first to find legislation → then use mevzuatId from results with:

  • get_mevzuat_content: Full document text

  • search_within_mevzuat: Search articles within a document

  • get_mevzuat_madde_tree: Table of contents / article tree

  • get_mevzuat_gerekce: Law rationale (if gerekceId is present in results)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
phraseNoFull-text search in document content (Solr/Lucene syntax). Searches inside the legislation text, not just the title. Leave empty to browse/list or use mevzuat_adi for title search. Solr operators: "exact phrase", +required -prohibited, wildcard*, single?, fuzzy~, fuzzy~N, "proximity"~N, boost^N. NOTE: AND/OR/NOT do NOT work here - use +term1 +term2 instead of term1 AND term2, use -term instead of NOT term, use 'term1 term2' (space) instead of term1 OR term2. Examples: 'ticaret' (simple), '"katma değer vergisi"' (exact phrase), '+yatırımcı +tazmin' (both required), 'yatırımcı -kurum' (exclude), 'yatırım*' (wildcard), '*ımcı' (leading wildcard), 'yatırımc?' (single char wildcard), 'yatırımcı~' (fuzzy), 'yatırımcı~2' (fuzzy with distance), '"yatırımcı tazmin"~5' (proximity within 5 words), 'yatırımcı^2 tazmin' (boost first term)
mevzuat_adiNoTitle/keyword search (Aranacak Kavram). Searches in legislation title/name. Use Turkish keywords, not law numbers. Multiple words are AND-matched (all must appear in title). Supports only: simple keywords, trailing wildcard (ticar*), single char wildcard (ticare?). For exact phrase match use tamCumle=True instead of quotes. Do NOT use quotes, +, -, ~, ^, or other Solr operators here (they break the search). Examples: 'ticaret kanunu', 'ceza', 'gümrük', 'sermaye piyasası', 'gelir vergisi', 'ticar*'. Can be used alone or together with phrase for combined filtering.
mevzuat_noNoLegislation number filter. Directly filters by the official number. E.g., '5237' for Türk Ceza Kanunu, '6102' for Türk Ticaret Kanunu, '6362' for Sermaye Piyasası Kanunu.
mevzuat_turNoFilter by legislation type. Leave empty to search all types. Single type or comma-separated for multiple types. Types: KANUN (Kanunlar), CB_KARARNAME (Cumhurbaşkanı Kararnameleri), YONETMELIK (Bakanlar Kurulu Yönetmelikleri), CB_YONETMELIK (Cumhurbaşkanlığı Yönetmelikleri), CB_KARAR (Cumhurbaşkanı Kararları), CB_GENELGE (Cumhurbaşkanlığı Genelgeleri), KHK (Kanun Hükmünde Kararnameler), TUZUK (Tüzükler), KKY (Kurum ve Kuruluş Yönetmelikleri), UY (Üniversite Yönetmelikleri), TEBLIGLER (Tebliğler), MULGA (Mülga Mevzuat). Examples: 'KANUN', 'KANUN,KHK', 'TEBLIGLER,KKY'
basliktaAraNoWhen True (default), mevzuat_adi searches only in legislation titles. When False, mevzuat_adi searches in both title and content.
tamCumleNoExact phrase match for mevzuat_adi. When True, the entire mevzuat_adi text must appear as an exact phrase. When False (default), individual words are matched. Example: 'katma değer vergisi' with tamCumle=True finds only exact matches.
resmi_gazete_tarihi_startNoStart date filter for Official Gazette date range (DD/MM/YYYY format). Filters legislation published on or after this date. E.g., '01/01/2024' to find legislation from 2024 onwards. Use with resmi_gazete_tarihi_end for a specific date range.
resmi_gazete_tarihi_endNoEnd date filter for Official Gazette date range (DD/MM/YYYY format). Filters legislation published on or before this date. E.g., '31/12/2024' to find legislation up to end of 2024. Use with resmi_gazete_tarihi_start for a specific date range.
resmi_gazete_sayisiNoOfficial Gazette issue number filter. E.g., '28513'.
pageNoPage number (1-based, default: 1)
page_sizeNoResults per page (1-100, default: 25)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations, so description carries full burden. It explains search modes, date range formatting, pagination, and Solr syntax. Lacks auth/rate limit info but is otherwise transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is long and detailed with structured sections, but some parts like Solr syntax examples are verbose. Could be more concise while retaining clarity.

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?

Covers all major aspects: search modes, date filtering, workflow. Mentions mevzuatId in results hinting at output. Given complexity, it is adequately complete.

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

Parameters5/5

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

Schema description coverage is 100%. Description adds significant context beyond schema, including Solr syntax examples, date usage, and operator explanations for each parameter.

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?

The description clearly states it searches/browses Turkish legislation on a specific site, lists 12 legislation types, and distinguishes from sibling tools by being a general search across all types.

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?

Provides explicit workflow: use this tool first, then use specific tools with mevzuatId. Recommends search modes but does not explicitly exclude use when sibling tools are more appropriate for specific types.

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/mevzuat-mcp'

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