Skip to main content
Glama

Belediye açık veri arama

opendata_search

Search Istanbul (İBB) and İzmir metropolitan municipality open datasets by keyword; returns matching dataset and resource IDs, flagging resources that can be queried next.

Instructions

Search open datasets of Istanbul (İBB) or İzmir metropolitan municipalities (açık veri): transport, dams/baraj, markets/hal, environment, disaster areas… Returns datasets and their resource ids; resources marked queryable can be read with opendata_query.

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": {
      "portal": "<portal>",
      "sorgu": "<sorgu>"
    },
    "name": "opendata_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
sorguYesArama, ör. "baraj doluluk", "hal fiyat", "toplanma alanı"
portalYesibb: İstanbul (data.ibb.gov.tr) · izmir: İzmir (acikveri.bizizmir.com)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose the return shape (datasets plus their resource ids) and a key behavioral flag (queryable resources). It does not mention pagination/limit behavior or source availability differences between the two portals, which would matter for a no-annotation tool.

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 with no wasted words, packing scope, covered topics, and the return-plus-follow-up behavior. The trailing ellipsis and parenthetical Turkish terms make it slightly dense but not confusing.

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 simple three-parameter search with no output schema, the description covers what it searches, over which portals, what it returns, and how results chain into opendata_query. Only the limit/pagination behavior and per-portal coverage differences remain undocumented.

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 67%, and the schema already documents the portal enum with URLs and gives example queries for sorgu. The description's list of domains adds thematic context but does not explain the required sorgu/portal semantics beyond what the schema provides, and says nothing about limit.

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?

States a specific verb and resource ("Search open datasets" of İBB/İzmir) plus the covered domains and what comes back (datasets and resource ids). This clearly distinguishes it from the sibling opendata_query, which the description names as the follow-up for reading queryable resources.

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 closing clause routes the agent to opendata_query when a resource is marked queryable, giving a clear use condition and alternative. It lacks an explicit when-not statement (e.g., when to skip the search and go straight to a known resource id), so it stops short of full guidance.

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