Skip to main content
Glama
saidsurucu

Mevzuat MCP

by saidsurucu

get_teblig_content

Retrieve the full Markdown content of a Turkish communiqué using its number and series from a prior search. Ready for analysis or summarization.

Instructions

Retrieve the full content of a Turkish communiqué (Tebliğ) in Markdown format.

This tool fetches the complete text of a communiqué identified by its number. Use 'search_teblig' first to find the communiqué number and series.

Returns:

  • Full communiqué content formatted as Markdown

  • Ready for analysis, summarization, or question answering

Example usage:

  1. Search for communiqués: search_teblig(aranacak_ifade="katma değer vergisi")

  2. Get full content: get_teblig_content(mevzuat_no="42331", mevzuat_tertip="5")

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mevzuat_noYesThe communiqué number from search results (e.g., '42331')
mevzuat_tertipNoCommuniqué series from search results (e.g., '5')5

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
madde_idYes
mevzuat_idYes
markdown_contentYes
error_messageNo

Implementation Reference

  • The handler for the 'get_teblig_content' tool. It is registered as a FastMCP tool via @app.tool() decorator. It accepts mevzuat_no and mevzuat_tertip parameters, calls mevzuat_client.get_content() with mevzuat_tur=9 (Tebliğ type), and returns MevzuatArticleContent (full communiqué content in Markdown).
    @app.tool()
    async def get_teblig_content(
        mevzuat_no: str = Field(
            ...,
            description="The communiqué number from search results (e.g., '42331')"
        ),
        mevzuat_tertip: str = Field(
            "5",
            description="Communiqué series from search results (e.g., '5')"
        )
    ) -> MevzuatArticleContent:
        """
        Retrieve the full content of a Turkish communiqué (Tebliğ) in Markdown format.
    
        This tool fetches the complete text of a communiqué identified by its number.
        Use 'search_teblig' first to find the communiqué number and series.
    
        Returns:
        - Full communiqué content formatted as Markdown
        - Ready for analysis, summarization, or question answering
    
        Example usage:
        1. Search for communiqués: search_teblig(aranacak_ifade="katma değer vergisi")
        2. Get full content: get_teblig_content(mevzuat_no="42331", mevzuat_tertip="5")
        """
        logger.info(f"Tool 'get_teblig_content' called: {mevzuat_no}, tertip: {mevzuat_tertip}")
    
        try:
            result = await mevzuat_client.get_content(
                mevzuat_no=mevzuat_no,
                mevzuat_tur=9,  # Tebliğ
                mevzuat_tertip=mevzuat_tertip
            )
    
            if result.error_message:
                logger.warning(f"Error fetching communiqué content: {result.error_message}")
    
            return result
    
        except Exception as e:
            logger.exception(f"Error in tool 'get_teblig_content' for {mevzuat_no}")
            return MevzuatArticleContent(
                madde_id=mevzuat_no,
                mevzuat_id=mevzuat_no,
                markdown_content="",
                error_message=f"An unexpected error occurred: {str(e)}"
            )
  • The tool is registered with FastMCP using the @app.tool() decorator on line 509. The MCP server instance is created at line 38 as 'app = FastMCP(name="MevzuatGovTrMCP", ...)'.
    @app.tool()
    async def get_teblig_content(
        mevzuat_no: str = Field(
            ...,
            description="The communiqué number from search results (e.g., '42331')"
        ),
        mevzuat_tertip: str = Field(
            "5",
            description="Communiqué series from search results (e.g., '5')"
        )
    ) -> MevzuatArticleContent:
  • The return type schema for get_teblig_content. MevzuatArticleContent is a Pydantic BaseModel with fields: madde_id, mevzuat_id, markdown_content, and optional error_message.
    class MevzuatArticleContent(BaseModel):
        """Model for the content of legislation (reused from old models)."""
        madde_id: str
        mevzuat_id: str
        markdown_content: str
        error_message: Optional[str] = None
Behavior3/5

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

No annotations are provided, so the description carries full burden. It states the tool returns Markdown content and is ready for analysis, implying read-only behavior, but does not explicitly mention no side effects or any authentication/rate limits. A simple fetch tool, but could be more explicit.

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 (3 sentences plus example) and front-loaded with the purpose. Every sentence adds value, and the example usage clarifies the workflow. No unnecessary text.

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 (though not detailed), so the description need not explain return format. It mentions Markdown and readiness for analysis. Given the simple retrieval nature and sibling context, it is fairly complete, though error handling or availability info is missing.

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 coverage is 100%, so baseline is 3. The description's parameter guidance ('The communiqué number from search results (e.g., '42331')') mirrors the schema descriptions exactly, adding no new semantic value beyond what the schema already provides.

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 retrieves full content of a Turkish communiqué in Markdown format, with a specific verb ('Retrieve') and resource ('Turkish communiqué (Tebliğ)'). It distinguishes itself from sibling tools that handle other document types (e.g., get_cbgenelge_content, get_mevzuat_content) or search functions.

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 advises to use 'search_teblig' first to find the communiqué number and series, providing a clear usage workflow (search then get content). It does not list exclusions or when not to use, but the context is clear given siblings.

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