Skip to main content
Glama

Eczane bul

find_pharmacies
Read-onlyIdempotent

Locate pharmacies in an İzmir district sorted by proximity to the district center, or find the nearest pharmacies to a latitude/longitude, including on-duty options by default.

Instructions

İzmir'de bir ilçedeki (ör. 'Buca', 'Bornova') eczaneleri ilçe merkezine yakınlığa göre listeler. Varsayılan olarak bugünün NÖBETÇİ eczanelerini döndürür (on_duty=false: tüm eczaneler). İlçe yerine lat/lon verilirse o noktaya en yakınları döndürür.

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": "find_pharmacies"
  }
}

Input Schema

NameRequiredDescriptionDefault
latNoEnlem (isteğe bağlı)
lonNoBoylam (isteğe bağlı)
limitNo
on_dutyNoSadece nöbetçi eczaneler
districtNoİzmir ilçesi, ör. 'Buca'

Output Schema

NameRequiredDescriptionDefault
metaYes
errorNo
on_dutyYes
districtNo
pharmaciesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and open-world, so safety is covered; the description usefully adds the default filtering behavior and the ordering rule above what annotations provide. It does not cover error behavior for unknown districts or whether results are capped by geography.

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 tight sentences, front-loaded with the primary behavior, then defaults, then the alternate input mode. No redundant restatement of the title or name.

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?

With annotations covering the safety profile and an output schema covering return values, the description only needs to explain the two lookup modes and defaults, which it does. The only gap is the behavior when no location argument is provided at all.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 80%, so the schema already documents most parameters; the description still adds real meaning by explaining that lat/lon is an alternative to district rather than an additional filter, and by restating the on_duty default semantics. The limit parameter is left entirely to the schema.

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 opens with a specific verb and resource ('İzmir'de bir ilçedeki ... eczaneleri listeler'), states the sort order (proximity to district center), and immediately covers the alternate geo-mode. The resource is unambiguous and cannot be confused with the sibling transit tool.

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 clearly explains the default mode (today's on-duty pharmacies), how to widen to all pharmacies (on_duty=false), and how to switch from district lookup to lat/lon nearest lookup. It lacks an explicit statement of when not to use the tool or what happens if neither district nor coordinates are supplied.

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

Deploy Server

Other Tools