Skip to main content
Glama
saidsurucu

Mevzuat MCP

by saidsurucu

search_within_khk

Search articles within a Turkish Decree Law (KHK) by keyword with Boolean operators or by natural language semantic search.

Instructions

Search within a specific Decree Law's (KHK) 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: "kanun AND değişiklik", '"kanun hükmünde"', "bakanlık OR kurum" Semantic examples: "sağlık alanında yapılan düzenlemeler", "anayasa değişikliği"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mevzuat_noYesThe KHK number to search within (e.g., '703', '700', '665')
keywordYesSearch query. For keyword mode: supports AND/OR/NOT operators (uppercase). For semantic mode: use natural language.
mevzuat_tertipNoKHK 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
Behavior4/5

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

Discloses mode behavior, operator support, case sensitivity, max results limit, and environment variable dependency. No annotations provided, so description compensates well. Could mention authentication or rate limits, but overall 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?

Concise two-paragraph structure with clear separation of modes, examples, and parameters. No unnecessary words; every sentence adds value.

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 sibling richness and presence of output schema, description is nearly complete. Could briefly state that it returns matching articles from the specified KHK, but context is sufficient for usage.

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 has 100% description coverage, but description adds value by explaining modes with examples, clarifying that case_sensitive only applies to keyword mode, and providing defaults and ranges. Adds meaning beyond schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 KHK's articles using keyword or semantic search. However, it does not explicitly differentiate from the sibling tool 'search_khk', which likely searches across multiple KHKs. The description implies but does not contrast.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Describes two modes and their requirements (e.g., OPENROUTER_API_KEY for semantic), but does not explicitly state when to use this tool vs. alternatives like 'search_khk' or other 'search_within_*' tools. Usage is implied but not directly guided.

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