Skip to main content
Glama
saidsurucu

Mevzuat MCP

by saidsurucu

search_within_cbk

Find specific articles within a Turkish Presidential Decree using keyword search with Boolean operators or natural language semantic search.

Instructions

Search within a specific Presidential Decree's 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: "organize AND suç", '"organize suç"', "devlet OR kamu" Semantic examples: "organize suç örgütleri ile mücadele", "bakanlık teşkilat yapısı"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mevzuat_noYesThe Presidential Decree number to search within (e.g., '1', '32')
keywordYesSearch query. For keyword mode: supports AND/OR/NOT operators (uppercase). For semantic mode: use natural language.
mevzuat_tertipNoDecree 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?

No annotations provided, so the description carries full burden. It clearly describes two search modes, Boolean operator usage, and the API key dependency. It could mention rate limits or result handling, but the core behaviors are 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 concise, well-structured with a clear overview, mode breakdown, and examples. Every sentence adds value, and the formatting improves readability.

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 tool's complexity (two search modes, 6 parameters), the description covers modes, constraints, and examples. An output schema exists (not shown), so return values need not be explained. Minor missing details like error handling are acceptable.

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?

Input schema has 100% coverage, but the description adds value by explaining mode-specific behavior (e.g., case_sensitive only in keyword mode, semantic mode requiring API key) and providing examples. This goes beyond the schema 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?

The description clearly states the tool searches within a specific Presidential Decree's articles using keyword or semantic search. It includes specific verbs ('search within') and explicitly distinguishes from sibling tools by focusing on a single decree vs. broad search.

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 explains two modes with examples and notes the OPENROUTER_API_KEY requirement for semantic mode. However, it does not explicitly state when to prefer this tool over siblings like 'search_cbk', though the naming and context imply it.

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