bim-mcp

bim_list_cities

Lists the 81 Turkish provinces available in BİM's store finder with their IDs and names, enabling users to identify provinces for location-based queries.

Instructions

The 81 Turkish provinces in BİM's store finder (id + name), as published on bim.com.tr. Note: per-city store addresses are NOT available — the finder lookup is session-gated on the site. No arguments.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 12, 2026

TDQS

A4.3/5.0

Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does disclose meaningful traits: the data provenance (published on bim.com.tr), the exact payload shape (id + name), and a hard limitation that per-city store addresses cannot be retrieved because the site's lookup is session-gated. It omits any mention of rate limits, caching, or freshness, which keeps it below a 5.

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?

Three short sentences, front-loaded with the resource and scope, followed by the critical limitation. The line breaks are slightly awkward but every sentence carries information an agent needs; nothing is redundant.

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?

An output schema exists, so return values need no further explanation, and the tool's complexity is low (no arguments, flat data). The description still supplies the one thing that could cause misuse — the unavailability of store addresses — leaving only minor gaps like data freshness or caching behavior.

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?

The tool takes zero parameters and the description confirms this with 'No arguments.', so there is nothing for the schema to explain. Baseline for a parameterless tool applies, with no gap to compensate for.

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 (list the 81 Turkish provinces in BİM's store finder) and pins down the returned fields as id + name, plus the source domain bim.com.tr. An agent can immediately tell this apart from sibling tools like bim_list_categories or bim_aktuel_products.

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?

Gives a clear usage context (enumerating provinces for the store finder) and an explicit exclusion: per-city store addresses are NOT available because the lookup is session-gated. It does not name an alternative tool for address-type lookups, so it stops short of full when/when-not routing.

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

Deploy Server