Skip to main content
Glama

Nöbetçi eczaneler

eczane_get_on_duty

Find today's on-duty pharmacies in supported Turkish provinces. Provide a city, plus a district for İstanbul, to get pharmacy names, addresses, phone numbers, directions and map links.

Instructions

On-duty pharmacies today (nöbetçi eczane) from official pharmacists' chambers. Supported provinces: İstanbul, Yalova, Ankara, İzmir, Adana, Mersin. District (ilçe) is required for İstanbul. Returns name, address, phone (where published), directions and map link.

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": {
      "il": "<il>"
    },
    "name": "eczane_get_on_duty"
  }
}

Input Schema

NameRequiredDescriptionDefault
ilYesİl: İstanbul, Yalova, Ankara, İzmir, Adana, Mersin
ilceNoİlçe (İzmir için semt de olur), ör. "Kadıköy", "Çankaya", "Bornova"
limitNoEn fazla kaç kayıt döndürülsün (1–200, varsayılan 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does reasonably well: it discloses the data source (official chambers), the temporal scope (today only), the province whitelist, the conditional district requirement, and that phone is only present 'where published'. It does not describe failure behavior for unsupported provinces or what happens when limit truncates results.

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, each load-bearing: resource and source first, then scope constraints, then return shape. There is no filler, no repetition of the title, and the most decision-relevant constraint (supported provinces, İstanbul district rule) appears before the return-value sentence.

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 three-parameter, read-only lookup with no output schema, the description covers the essentials: scope, source, valid inputs, conditional requirement, and the fields returned (name, address, phone, directions, map link). Missing only edge-case behavior for unsupported provinces or empty results.

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 the parameters are already documented, and the baseline is 3. The description does add one genuinely new constraint the schema does not express — that district is required for İstanbul — but that is the only semantic addition; province and limit carry no extra meaning.

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 names a specific resource and subset ('On-duty pharmacies today (nöbetçi eczane)') plus the upstream source ('official pharmacists' chambers'), so an agent knows exactly what data is returned and that it is limited to the current day. It also enumerates supported provinces and the required district condition, making the tool unambiguous even against a large sibling catalog.

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?

It gives clear operating context: the result is 'today' only (so it is not a historical lookup), the province must be one of six supported values, and district is mandatory for İstanbul. It stops short of naming an alternative tool or stating what to do when an unsupported province is requested, so it is strong but not complete when/when-not guidance.

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