Skip to main content
Glama
saidsurucu

Mevzuat MCP

by saidsurucu

search_within_tuzuk

Search specific Turkish statutes' articles using keyword queries with Boolean operators or semantic AI search for natural language questions.

Instructions

Search within a specific Statute's (Tüzük) articles using keyword or semantic search.

Modes:

  • semantic=False (default): Keyword search with Boolean operators (AND/OR/NOT, uppercase required)

  • semantic=True: Natural language semantic search using AI embeddings (requires OPENROUTER_API_KEY)

Keyword examples: "tapu AND sicil", '"sicil kayıt"', "tescil OR ilan" Semantic examples: "tapu sicil kayıt işlemleri", "vakıf tescil süreci"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mevzuat_noYesThe statute number to search within (e.g., '20135150', '20134513', '200814001')
keywordYesSearch query. For keyword mode: supports AND/OR/NOT operators (uppercase). For semantic mode: use natural language.
mevzuat_tertipNoStatute series from search results (e.g., '5')5
case_sensitiveNoWhether to match case when searching (default: False). Only used in keyword mode.
max_resultsNoMaximum number of matching articles to return (1-50, default: 25)
semanticNoTrue: semantic search (natural language query, requires OPENROUTER_API_KEY). False: keyword search (Boolean operators AND/OR/NOT).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations provided, so description fully covers behavior: two search modes, Boolean operators, case sensitivity, max results, API key requirement. Examples clarify usage.

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?

Concise, front-loaded, uses headings for modes. Every sentence adds value. Examples are well-structured.

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?

Covers all aspects: required inputs, mode selection, parameter details, examples. With 6 parameters and no annotations, description is complete.

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 already describes all parameters (100% coverage). Description adds value with usage examples, operator uppercase requirement, and API key condition for semantic mode.

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?

Clearly states the tool searches within a specific statute's articles using keyword or semantic search. Distinguishes from siblings by specifying 'Tüzük' and requiring a statute number.

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?

Explains two modes and gives examples. Implicitly requires statute number (mevzuat_no). Does not explicitly compare to other tools like search_tuzuk, but provides context on mode selection.

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