Skip to main content
Glama
saidsurucu

Yargı MCP

by saidsurucu
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Local

search_anayasa_unified

Read-onlyIdempotent

Retrieve Turkish Constitutional Court decisions by selecting norm control or individual application type and entering keywords.

Instructions

Use this when searching Turkish Constitutional Court decision records. Supports norm control decisions and individual application decisions. Norm control filters include reviewed norm metadata; results are court decisions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keywordsNoKeywords for full-text search (joined into a single query)
decision_typeYesDecision type: norm_denetimi (norm control) or bireysel_basvuru (individual applications)
page_to_fetchNoPage number to fetch (1-100)
results_per_pageNoResults per page (1-100)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed11 schema fields changedv0.2.2
    • removedInput schema / properties / application_date_end
      Removed value: -{
-  "default": "",
-  "description": "Application end date (norm_denetimi only)",
-  "type": "string"
-}
    • removedInput schema / properties / application_date_start
      Removed value: -{
-  "default": "",
-  "description": "Application start date (norm_denetimi only)",
-  "type": "string"
-}
    • removedInput schema / properties / decision_end_date
      Removed value: -{
-  "default": "",
-  "description": "Decision end date (bireysel_basvuru only)",
-  "type": "string"
-}
    • removedInput schema / properties / decision_start_date
      Removed value: -{
-  "default": "",
-  "description": "Decision start date (bireysel_basvuru only)",
-  "type": "string"
-}
    • removedInput schema / properties / decision_type_norm
      Removed value: -{
-  "default": "ALL",
-  "description": "Decision type for norm denetimi",
-  "enum": [
-    "ALL",
-    "1",
-    "2",
-    "3"
-  ],
-  "type": "string"
-}
    • changedInput schema / properties / keywords / description
      Previous value: -"Keywords to search for (common parameter)"New value: +"Keywords for full-text search (joined into a single query)"
    • removedInput schema / properties / keywords_all
      Removed value: -{
-  "description": "All keywords must be present (norm_denetimi only)",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}
    • removedInput schema / properties / keywords_any
      Removed value: -{
-  "description": "Any of these keywords (norm_denetimi only)",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}
    • removedInput schema / properties / norm_type
      Removed value: -{
-  "default": "ALL",
-  "description": "Norm type (bireysel_basvuru only)",
-  "enum": [
-    "ALL",
-    "1",
-    "2",
-    "3",
-    "4",
-    "5",
-    "6",
-    "7",
-    "8",
-    "9",
-    "10",
-    "11",
-    "12",
-    "13",
-    "14",
-    "0"
-  ],
-  "type": "string"
-}
    • addedInput schema / properties / results_per_page
      Added value: +{
+  "default": 10,
+  "description": "Results per page (1-100)",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}
    • removedInput schema / properties / subject_category
      Removed value: -{
-  "default": "",
-  "description": "Subject category (bireysel_basvuru only)",
-  "type": "string"
-}
  2. Changed14 schema fields changedv1.0.0
    • removedInput schema / properties / application_date_end / title
      Removed value: -"Application Date End"
    • removedInput schema / properties / application_date_start / title
      Removed value: -"Application Date Start"
    • removedInput schema / properties / decision_end_date / title
      Removed value: -"Decision End Date"
    • removedInput schema / properties / decision_start_date / title
      Removed value: -"Decision Start Date"
    • removedInput schema / properties / decision_type / title
      Removed value: -"Decision Type"
    • removedInput schema / properties / decision_type_norm / title
      Removed value: -"Decision Type Norm"
    • removedInput schema / properties / keywords / title
      Removed value: -"Keywords"
    • removedInput schema / properties / keywords_all / title
      Removed value: -"Keywords All"
    • removedInput schema / properties / keywords_any / title
      Removed value: -"Keywords Any"
    • removedInput schema / properties / norm_type / title
      Removed value: -"Norm Type"
    • removedInput schema / properties / page_to_fetch / title
      Removed value: -"Page To Fetch"
    • removedInput schema / properties / subject_category / title
      Removed value: -"Subject Category"
    • removedOutput schema / properties / result / title
      Removed value: -"Result"
    • removedOutput schema / title
      Removed value: -"_WrappedResult"
  3. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations (readOnlyHint, openWorldHint, idempotentHint) already cover safety and idempotency. The description adds minor context (norm control filters include reviewed norm metadata) but does not expand on behavioral implications beyond what annotations provide. No contradictions.

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 extremely concise: two sentences, no wasted words. The key instruction ('Use this when...') is front-loaded, making it efficient for an agent to parse.

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?

The tool has an output schema, so the description need not explain return values. It covers the search domain (Turkish Constitutional Court decisions), decision types, and pagination. Minor gap: could mention that results are a list of documents, but output schema likely covers that.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all four parameters. The description adds minimal additional meaning (e.g., 'norm control filters include reviewed norm metadata'), but this is vague and not necessary. Baseline score of 3 is appropriate.

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 Turkish Constitutional Court decision records, specifying the two decision types (norm control and individual applications). The name and description differentiate it from sibling search tools targeting other courts/agencies.

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 explicitly says 'Use this when searching Turkish Constitutional Court decision records', providing clear context. However, it does not explicitly state when not to use it or mention alternatives, though the sibling list implies other tools for other domains.

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/yargi-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server