Skip to main content
Glama
saidsurucu

Yargı MCP

by saidsurucu
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Local

get_rekabet_kurumu_document

Read-onlyIdempotent

Retrieve the full text of a Turkish Competition Authority decision. Get paginated Markdown content using the decision's GUID.

Instructions

Use this when retrieving full text of a Competition Authority decision. Returns paginated Markdown format.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
karar_idYesGUID (kararId) of the Rekabet Kurumu decision. This ID is obtained from search results.
page_numberNoRequested page number for the Markdown content converted from PDF (1-indexed, accepts int). Default is 1.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

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

  1. Changed7 schema fields changedv1.0.0
    • removedInput schema / properties / karar_id / title
      Removed value: -"Karar Id"
    • removedInput schema / properties / page_number / title
      Removed value: -"Page Number"
    • addedOutput schema / additionalProperties
      Added value: +true
    • removedOutput schema / description
      Removed value: -"Model for a Rekabet Kurumu decision document.\nContains metadata from the landing page, a link to the PDF,\nand the PDF's content converted to paginated Markdown."
    • removedOutput schema / properties
      Removed value: -{
-  "current_page": {
-    "default": 1,
-    "description": "Page",
-    "title": "Current Page",
-    "type": "integer"
-  },
-  "error_message": {
-    "anyOf": [
-      {
-        "type": "string"
-      },
-      {
-        "type": "null"
-      }
-    ],
-    "default": null,
-    "description": "Error",
-    "title": "Error Message"
-  },
-  "is_paginated": {
-    "default": false,
-    "description": "Paginated",
-    "title": "Is Paginated",
-    "type": "boolean"
-  },
-  "karar_id": {
-    "description": "ID",
-    "title": "Karar Id",
-    "type": "string"
-  },
-  "markdown_chunk": {
-    "anyOf": [
-      {
-        "type": "string"
-      },
-      {
-        "type": "null"
-      }
-    ],
-    "default": null,
-    "description": "Content",
-    "title": "Markdown Chunk"
-  },
-  "pdf_url": {
-    "anyOf": [
-      {
-        "format": "uri",
-        "maxLength": 2083,
-        "minLength": 1,
-        "type": "string"
-      },
-      {
-        "type": "null"
-      }
-    ],
-    "default": null,
-    "description": "PDF URL",
-    "title": "Pdf Url"
-  },
-  "source_landing_page_url": {
-    "description": "Source URL",
-    "format": "uri",
-    "maxLength": 2083,
-    "minLength": 1,
-    "title": "Source Landing Page Url",
-    "type": "string"
-  },
-  "title_on_landing_page": {
-    "anyOf": [
-      {
-        "type": "string"
-      },
-      {
-        "type": "null"
-      }
-    ],
-    "default": null,
-    "description": "Title",
-    "title": "Title On Landing Page"
-  },
-  "total_pages": {
-    "default": 1,
-    "description": "Total pages",
-    "title": "Total Pages",
-    "type": "integer"
-  }
-}
    • removedOutput schema / required
      Removed value: -[
-  "source_landing_page_url",
-  "karar_id"
-]
    • removedOutput schema / title
      Removed value: -"RekabetDocument"
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The description adds valuable behavioral context beyond annotations by specifying the output format ('paginated Markdown format') and the pagination mechanism. While annotations already declare readOnlyHint=true and idempotentHint=true, the description usefully clarifies the document conversion process ('converted from PDF') and pagination behavior.

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 perfectly concise with two sentences that each earn their place: the first establishes purpose and context, the second specifies output format. No wasted words, and the most important information is front-loaded.

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 the tool's moderate complexity, comprehensive annotations (readOnlyHint, idempotentHint), complete schema documentation, and the presence of an output schema, the description provides exactly what's needed: clear purpose, usage context, and key behavioral details about format and pagination.

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?

With 100% schema description coverage, the schema already fully documents both parameters. The description doesn't add any additional parameter semantics beyond what's in the schema, so it meets the baseline expectation without exceeding it.

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 specific action ('retrieving full text'), resource ('Competition Authority decision'), and output format ('paginated Markdown format'), distinguishing it from sibling search tools like 'search_rekabet_kurumu_decisions' which likely return metadata rather than full document content.

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 provides clear context about when to use this tool ('when retrieving full text of a Competition Authority decision'), but doesn't explicitly mention when not to use it or name specific alternatives among the many sibling tools, though the distinction from search tools is implied.

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