Skip to main content
Glama
saidsurucu

Mevzuat MCP

by saidsurucu

search_teblig

Search Turkish communiqués by keyword in titles and content on mevzuat.gov.tr. Supports Boolean operators and exact phrase matching for precise results.

Instructions

Search for Turkish communiqués (Tebliğ) in both titles and content on mevzuat.gov.tr.

IMPORTANT: Search is keyword-based, NOT by number. Use descriptive Turkish terms. Communiqués are regulatory documents issued by various government institutions.

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

Example queries:

  • "katma değer vergisi" - Find VAT-related communiqués

  • "muafiyet OR istisna" - Communiqués about exemptions

  • "gümrük" - Customs-related communiqués

  • "ithalat" or "ihracat" - Import/export communiqués

Returns: Communiqué number, title, publication date, Official Gazette info.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
aranacak_ifadeYesSearch query with optional Boolean operators: simple word (vergi), AND (vergi AND muafiyet), OR (muafiyet OR istisna), NOT (vergi NOT gelir), + for required (+term), grouping with (), exact phrase with quotes ("katma değer vergisi")
tam_cumleNoExact phrase match (true) or any word match (false, default). Set to true when searching for exact phrases.
baslangic_tarihiNoStart year for filtering results (format: YYYY, e.g., '2020')
bitis_tarihiNoEnd year for filtering results (format: YYYY, e.g., '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
Behavior3/5

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

With no annotations, description carries full burden. It explains search behavior (keyword-based, exact phrase option) and return fields, but omits details on pagination limits, result ordering, or whether the operation is read-only.

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?

Description is well-structured: purpose, important note, syntax, examples, returns. Examples are helpful but add length; still concise and front-loaded with critical information.

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 output schema exists, description appropriately states return fields. All parameters are documented. Missing details on potential errors or data volume, but sufficient for a search tool with clear purpose and good annotation coverage.

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 descriptions already cover all 7 parameters (100% coverage). Description adds value by explaining the query syntax and providing examples, which go beyond the schema's parameter descriptions.

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 the tool searches for Turkish communiqués (Tebliğ) in titles and content on mevzuat.gov.tr, with specific verb 'search' and resource 'Tebliğ'. It distinguishes from sibling tools like search_kanun or search_khk by targeting a specific document type.

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?

Explicitly notes that search is keyword-based, not by number, guiding users to use descriptive Turkish terms. Provides query syntax and examples, but does not explicitly mention alternative tools like get_teblig_content for number-based lookups.

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