Skip to main content
Glama
saidsurucu

Mevzuat MCP

by saidsurucu

search_khk

Search Turkish Decree Laws (KHKs) by keyword with Boolean operators, wildcards, and date filters. Retrieve KHK number, title, and official gazette information.

Instructions

Search for Turkish Decree Laws (Kanun Hükmünde Kararname / KHK) in titles and content.

IMPORTANT: Search is keyword-based, NOT by KHK number. Use descriptive Turkish terms. KHKs were abolished after the 2017 constitutional referendum (last issued 2018). Previously enacted KHKs remain in force unless repealed.

Query Syntax: Simple keyword, AND, OR, NOT, +required, (grouping), "exact phrase"

Example queries:

  • "sağlık AND düzenleme" - Health-related KHKs

  • "anayasa" - Constitutional KHKs

  • Leave empty with dates (e.g., 2010-2018) to list all KHKs from a period

Returns: KHK number, title, dates, Official Gazette info.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
aranacak_ifadeNoSearch query with Boolean operators and wildcards. Examples: "değişiklik" (simple), "sağlık AND düzenleme" (AND), "bakanlık OR kurum" (OR), "kanun NOT yürürlük" (NOT), "değişiklik*" (wildcard), "güvenlik sistemi" (exact phrase with quotes). Leave empty to list all KHKs in date range.
tam_cumleNoIf True, searches for exact phrase match. If False (default), searches for any word match with Boolean operators.
baslangic_tarihiNoStart year for filtering results (format: YYYY, e.g., '2010'). Use with bitis_tarihi to define a date range.
bitis_tarihiNoEnd year for filtering results (format: YYYY, e.g., '2018'). Use with baslangic_tarihi to define a date range.
page_numberNoPage number of results to retrieve (starts from 1)
aranacak_yerNoWhere to search: 1=Title only, 2=Content only, 3=Both title and content (default)
page_sizeNoNumber of results per page (1-100, default: 25)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
documentsYes
total_resultsYes
current_pageYes
page_sizeYes
total_pagesYes
query_usedYes
error_messageNo
Behavior4/5

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

With no annotations, the description discloses important behavioral traits: KHKs were abolished after 2017 but remain in force, and returns include KHK number, title, dates, and Official Gazette info. It does not cover pagination or error handling, but the core behavior is transparent.

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 description is well-structured with a brief intro, important notes, query syntax, examples, and return info. Every sentence serves a purpose; no fluff.

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?

Given the lack of output schema, the description mentions return fields. Parameter descriptions in schema cover pagination. The description could elaborate more on pagination behavior, but it is adequate for a search tool.

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?

All 7 parameters have descriptions in the schema (100% coverage). The description adds value by providing query syntax examples, explaining the tam_cumle and aranacak_yer parameters, and showing how to use date range parameters with examples.

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 Turkish Decree Laws (KHK) in titles and content, distinguishing it from sibling tools for other legal documents. It specifies keyword-based search and provides context on KHK abolition.

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?

The description explicitly says 'Search is keyword-based, NOT by KHK number' and advises using descriptive Turkish terms. It includes example queries and mentions leaving the query empty to list all KHKs, but does not explicitly state when to avoid this tool.

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