Skip to main content
Glama

Resmî Gazete günlük sayı

resmi_gazete_get_issue

Retrieve the Official Gazette of Türkiye's table of contents for today or a chosen date, including regulations, communiqués, decisions, circulars, and announcements with links; filter by keyword.

Instructions

Table of contents of the Official Gazette of Türkiye (Resmî Gazete) for today or a given date: regulations (yönetmelik), communiqués (tebliğ), presidential decisions (karar), circulars (genelge), announcements (ilan) with links. Optional keyword filter.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "resmi_gazete_get_issue"
  }
}

Input Schema

NameRequiredDescriptionDefault
aramaNoBaşlıklarda aranacak kelime, ör. "vergi", "yönetmelik"
tarihNoTarih (YYYY-MM-DD). Boşsa bugünkü sayı.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does well: it discloses the return shape (table of contents with links), the default date behavior ('today or a given date'), and the optional filtering. It omits behavioral detail about what happens on non-publication days (weekends/holidays), but for a read-only retrieval tool the disclosure is solid.

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?

A single front-loaded sentence that leads with the resource and purpose, then lists content types and the filter. The enumeration earns its place by telling the agent what sections to expect; wording is efficient with no filler.

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?

For a 2-optional-parameter read tool with no output schema and no annotations, the description covers purpose, date default, the keyword filter, and what the response contains (sections with links). Minor gaps around failure/empty-day behavior remain but the core is complete.

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 both parameters (tarih, arama) are already documented in the schema, including the format and the title-search semantics ('Başlıklarda aranacak kelime'). The description only restates 'today or a given date' and 'optional keyword filter' without adding format or syntax detail beyond the schema, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Table of contents of the Official Gazette of Türkiye') and enumerates the content types it returns (regulations, communiqués, decisions, circulars, announcements). This is clear, but it does not explicitly name or contrast with the sibling resmi_mevzuat_search, leaving the boundary implicit.

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

Usage Guidelines3/5

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

The 'for today or a given date' phrasing implies when to use it and clarifies the default, and mentions the optional keyword filter. However, it offers no explicit when-not guidance or named alternative (e.g., use resmi_mevzuat_search for cross-date legal search).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.