Skip to main content
Glama

Belediye açık veri tablosu sorgula

opendata_query

Read rows from İBB or İzmir open-data datastore resources by resource ID, with full-text filtering, sorting, and row limits for targeted data retrieval.

Instructions

Read rows from a queryable (datastore) resource of İBB or İzmir open data portals. Use opendata_search first to find the resource id. Supports full-text filter and sorting.

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>",
      "kaynakId": "<kaynakId>"
    },
    "name": "opendata_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoEn fazla kaç kayıt döndürülsün (1–200, varsayılan 20)
sorguNoTablo içinde tam metin arama
portalYesibb: İstanbul (data.ibb.gov.tr) · izmir: İzmir (acikveri.bizizmir.com)
siralaNoSıralama, ör. "_id desc" (en yeni kayıtlar)
kaynakIdYesopendata_search sonucundaki 'sorgulanabilir' kaynak id'si

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It establishes that this is a read operation and that full-text filtering and sorting are supported, but says nothing about result volume behavior beyond the limit, error handling for non-queryable resource ids, or portal-specific quirks. Adequate but thin for a tool with zero annotation coverage.

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?

Three short sentences, zero padding. The core action comes first, the prerequisite second, and the capabilities last, so an agent gets the essentials from the opening clause.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description should describe what a row result looks like or whether total counts are returned; 'Read rows' is the only hint given. For a 5-parameter data-retrieval tool that depends on a prior search call and portal-specific resource ids, this leaves a notable gap.

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 the portal enum and sort syntax is already documented in structured form. The description's mention of full-text filter and sorting only echoes what the schema says, adding no syntax or format detail beyond it — baseline 3 is appropriate.

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 — 'Read rows from a queryable (datastore) resource of İBB or İzmir open data portals' — which is a distinct operation from searching for resources. The parenthetical '(datastore)' and 'queryable' qualifier tell an agent this only works on a subset of resources, separating it cleanly from opendata_search.

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?

Explicitly routes the agent through opendata_search first to obtain the resource id, which is a real workflow prerequisite rather than an inference. It does not state when to avoid this tool (e.g., non-queryable resources), but the required sequencing is unambiguous.

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