Skip to main content
Glama

Yakındaki WiFi ve kütüphaneler

istanbul_city_services_nearby
Read-onlyIdempotent

Summarize WiFi near a static reference point and district-level libraries/culture.

district (all 39 Istanbul districts) is exclusive with place/coordinates; district-only place names also return district address lists, without WiFi or invented distances. Radius applies only to WiFi with a point. For Acıbadem, specify 'Acıbadem, Kadıköy' or 'Acıbadem, Üsküdar'. Not full address geocoding.

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

Input Schema

NameRequiredDescriptionDefault
latNo
lonNo
limitNo
placeNo
districtNo
radius_mNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish that this is a safe, read-only, idempotent operation. The description adds useful behavioral context beyond them: district-only queries may return address lists without WiFi or invented distances, and geocoding is not full address geocoding.

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?

The purpose is front-loaded, and the remaining sentences each add a concrete constraint or disambiguation rule. The examples and exclusions earn their place, and the description is appropriately sized for a six-parameter tool.

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?

The description covers usage constraints and some return behavior, but with no output schema it does not describe what the summarized WiFi/library results look like. It also leaves limit semantics undocumented, so an agent has gaps for correct invocation and result interpretation.

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?

With 0% schema description coverage, the description carries the burden and explains the main ambiguous inputs: district/place/coordinates exclusivity, radius applicability, and the Acıbadem disambiguation. It does not explain the limit parameter, but most semantically important parameters are covered.

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?

The description states a specific verb (summarize) and resources (WiFi and district-level libraries/culture), with scope near a reference point or district. It is clear enough to distinguish this from generic nearby tools, but it does not explicitly name alternatives such as istanbul_nearby or istanbul_mobility_nearby.

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 explicit constraints: district is exclusive with place/coordinates, district-only place names return address lists, radius only applies to WiFi with a point, and ambiguous names like Acıbadem need district qualification. It does not explicitly compare this tool against sibling tools, so it falls short of full alternative guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.