Skip to main content
Glama
saidsurucu

Mevzuat MCP

by saidsurucu

search_within_teblig

Search within a specific Turkish communiqué (Tebliğ) by number using keyword or semantic queries. Supports Boolean operators (AND/OR/NOT) and natural language.

Instructions

Search within a specific communiqué's (Tebliğ) content using keyword or semantic search.

Tries article-based splitting first; if no articles found, falls back to chunk-based 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: "vergi AND muafiyet", '"katma değer"', "istisna OR muafiyet" Semantic examples: "vergi muafiyeti koşulları", "KDV iade işlemleri"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mevzuat_noYesThe communiqué number to search within (e.g., '42331')
keywordYesSearch query. For keyword mode: supports AND/OR/NOT operators (uppercase). For semantic mode: use natural language.
mevzuat_tertipNoCommuniqué 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 segments 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. Description discloses fallback behavior (article-based then chunk-based), mode differences, and API key requirement. Lacks mention of cost or rate limits for semantic mode, 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?

Well-structured with clear sections (purpose, fallback, modes, examples). No redundant sentences; every part contributes useful 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 the tool's complexity (two modes, fallback, 6 params), the description covers key aspects. Output schema exists, so return values are not needed. Could mention pagination but not required.

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 with examples, mode explanations, and fallback details. Goes beyond the schema to clarify usage patterns.

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 it searches within a specific Tebliğ communiqué using keyword or semantic search. The verb 'search within' and resource 'teblig' are unambiguous, and the description distinguishes from sibling tools that search other document types.

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 explains two modes (keyword vs. semantic) with examples and the requirement of OPENROUTER_API_KEY for semantic mode. Provides fallback logic but does not explicitly differentiate from sibling tools like search_teblig, though the name indicates scope.

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