VeriApi.Pro

Search the Official Gazette archive

resmigazete_ara

Read-onlyIdempotent

Full-text search of Official Gazette items since 2005 by title or full text, with type, institution and date filters; returns matching items newest first or by relevance. Paid plans only.

Endpoint: GET /v1/resmigazete/ara. Requires a paid plan (free plan returns 403). Costs 2 request units per call. Read-only; JSON in Turkish with source and guncelleme (updated at) fields.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "<q>"
    },
    "name": "resmigazete_ara"
  }
}

Input Schema

Name	Required	Description	Default
`q`	Yes	Search words (all must match), "exact phrase" in quotes, -word to exclude.
`tur`	No	Comma-separated type codes: kanun, khk, cb_kararnamesi, cb_karari, genelge, yonetmelik, teblig, karar, tbmm_karari, andlasma, atama, yonerge, statu, yargi, ilan, diger.
`adet`	No	Results per page (default 20).
`bitis`	No	Latest gazette date, YYYY-MM-DD.
`kurum`	No	Issuing institution name or part of it, e.g. 'Sağlık Bakanlığı'.
`sayfa`	No	Page number, from 1.
`kapsam`	No	'baslik' (title only, default) or 'tum' (title + full text).	baslik
`sirala`	No	'tarih' (newest first, default) or 'ilgi' (relevance).	tarih
`baslangic`	No	Earliest gazette date, YYYY-MM-DD.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real value beyond them: the 403 on free plans, a concrete cost of 2 request units, Turkish-language JSON with source and guncelleme fields, and the default ordering. These are exactly the operational facts an agent needs before calling.

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?

Front-loads capability, then filters and ordering, then pricing and response shape; nearly every clause carries information. The endpoint string and request-unit pricing are dense but justified for an agent deciding whether to call.

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 9-parameter search tool with no output schema, it covers access constraints, cost, ordering, and the shape of returned records. It could say slightly more about pagination limits and result metadata, but nothing essential for correct invocation 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 description coverage is 100%, so every parameter (including query operators, type codes, kapsam, sirala, paging) is already documented in the schema. The description only restates the filter categories at a high level and adds no syntax or semantics 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 and resource ('Full-text search of Official Gazette items since 2005 by title or full text') plus the filter dimensions, so the agent knows exactly what is searched. It does not name or differentiate against the obvious sibling resmigazete_son (latest items), which keeps it short of a 5.

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?

Gives clear usage context: paid plans only, free plan returns 403, and 2 request units per call, which lets an agent decide whether to invoke. It stops short of explicit when-not guidance or directing the agent to resmigazete_son for simple latest-item lookups.

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

All VeriApi.Pro tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?