Skip to main content
Glama
saidsurucu

Mevzuat MCP

by saidsurucu

search_within_cbgenelge

Search within a Presidential Circular (CB Genelgesi) using keyword or semantic query. Provide the official gazette date from prior search results.

Instructions

Search within a specific Presidential Circular's (CB Genelgesi) content using keyword or semantic search.

Presidential Circulars are PDF-based and use chunk-based splitting (no article structure). IMPORTANT: resmi_gazete_tarihi is required (from search_cbgenelge results).

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: "koordinasyon AND toplantı", '"kamu yönetimi"' Semantic examples: "bakanlıklar arası koordinasyon düzeni", "tasarruf tedbirleri"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mevzuat_noYesThe Presidential Circular number to search within (e.g., '16', '15')
keywordYesSearch query. For keyword mode: supports AND/OR/NOT operators (uppercase). For semantic mode: use natural language.
resmi_gazete_tarihiYesOfficial Gazette date from search results in DD/MM/YYYY format (e.g., '20/09/2025') - REQUIRED for PDF retrieval
mevzuat_tertipNoCircular 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
Behavior5/5

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

With no annotations provided, the description fully carries the burden: it discloses the two search modes, API key requirement for semantic mode, boolean operator usage, and chunk-based splitting. No destructive or side effects are implied, and the behavior is clear.

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?

The description is well-structured with sections, examples, and important notes front-loaded. It is slightly verbose but every sentence adds meaning; no wasted words. It could be more succinct, but the clarity justifies the length.

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?

Given 7 parameters, an output schema, and no annotations, the description covers all essential aspects: search modes, prerequisites, parameter constraints, and mode-specific behavior. It is complete for an agent to correctly invoke the tool without confusion.

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%, so baseline is 3. The description adds value by providing examples for keyword and semantic queries, explaining the case sensitivity relevance, and clarifying that 'resmi_gazete_tarihi' is required from prior search results, which goes beyond bare 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 Circular using keyword or semantic search, differentiating it from sibling tools like 'search_cbgenelge' which finds circulars themselves. It also specifies the chunk-based document structure, making the purpose concrete.

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

Usage Guidelines5/5

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

It explicitly states that 'resmi_gazete_tarihi' is required and should come from 'search_cbgenelge' results, providing a clear prerequisite. It also explains the two modes (keyword vs semantic) and gives examples, leaving no ambiguity about when to use each.

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