Skip to main content
Glama
saidsurucu

Mevzuat MCP

by saidsurucu

search_kanun

Find Turkish laws (Kanun) on mevzuat.gov.tr by searching keywords in titles and content. Supports Boolean operators, exact phrase matching, and date range filtering.

Instructions

Search for Turkish laws (Kanun) in both titles and content on mevzuat.gov.tr.

IMPORTANT: Search is keyword-based, NOT by law number. Use descriptive Turkish terms.

  • WRONG: "3065" or "6362" (numbers won't find laws reliably)

  • RIGHT: "katma değer vergisi" (finds KDV Kanunu No. 3065)

  • RIGHT: "sermaye piyasası" (finds Sermaye Piyasası Kanunu No. 6362)

  • RIGHT: "gümrük kanunu" (finds Gümrük Kanunu No. 4458)

  • RIGHT: "gelir vergisi" (finds Gelir Vergisi Kanunu No. 193)

  • RIGHT: "ceza muhakemesi" (finds CMK No. 5271)

  • RIGHT: "vergi usul" (finds VUK No. 213)

Use 'search_within_kanun' to search within a specific law's articles after finding its number.

Query Syntax:

  • Simple keyword: yatırımcı

  • Boolean AND: yatırımcı AND tazmin (both terms required)

  • Boolean OR: yatırımcı OR müşteri (at least one term)

  • Boolean NOT: yatırımcı NOT kurum (first yes, second no)

  • Required term: +yatırımcı +tazmin (similar to AND)

  • Grouping: (yatırımcı OR müşteri) AND tazmin

  • Exact phrase: "mali sıkıntı" (or use tam_cumle=true)

Returns: Law number, title, acceptance date, Official Gazette date and issue number.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
aranacak_ifadeYesSearch query with optional Boolean operators: simple word (yatırımcı), AND (yatırımcı AND tazmin), OR (vergi OR ücret), NOT (yatırımcı NOT kurum), + for required (+term), grouping with (), exact phrase with quotes ("mali sıkıntı")
tam_cumleNoExact phrase match (true) or any word match (false, default). Set to true when searching for exact phrases like 'mali sıkıntı'.
baslangic_tarihiNoStart date for filtering results (format: DD.MM.YYYY, e.g., '01.01.2020')
bitis_tarihiNoEnd date for filtering results (format: DD.MM.YYYY, e.g., '31.12.2024')
page_numberNoPage number for pagination (starts at 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)

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?

No annotations provided, so the description fully carries the behavioral disclosure burden. It explains the search behavior (keyword-based), query syntax, and what is returned. While it covers most aspects well, it could mention pagination or result limits more explicitly.

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?

Well-structured with sections and bullet points, front-loading the purpose. While somewhat lengthy, every sentence contributes value. Minor redundancy in query syntax examples could be tightened, but overall good.

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 the output schema exists (though not shown), the description adequately covers all necessary aspects: purpose, usage, parameters, query syntax, and return fields. No significant gaps remain.

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

Parameters4/5

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

Schema description coverage is 100%, but the description adds significant value beyond schema definitions by explaining search philosophy, providing usage examples, and clarifying parameter meanings (e.g., aranacak_yer values). This goes beyond simply restating schema properties.

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 for Turkish laws (Kanun) in titles and content on mevzuat.gov.tr, with a specific verb and resource. It distinguishes from sibling tools like search_within_kanun, which is used to search within a specific law after finding its number.

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?

Provides explicit guidance that search is keyword-based, not by law number, with examples of correct and incorrect queries. Directs users to use search_within_kanun after obtaining the law number, clearly differentiating when to use this tool vs 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/mevzuat-mcp'

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