Skip to main content
Glama
ikea-mcp
by taejin5314

find_nearby_stores

Read-onlyIdempotent

Locate IKEA stores nearest to a given latitude and longitude, returning them sorted by distance. Use the store IDs for stock checks or to find the best store for an item or cart.

Instructions

Find the IKEA stores closest to a place. Pass the latitude and longitude of the user's city or address (an approximate city-centre coordinate is fine). Returns stores nearest first with the straight-line distance in km. Use the returned storeId values with the stock tools, or pass the same coordinates as near to find_best_store_for_item / find_best_store_for_cart.

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": {
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "find_nearby_stores"
  }
}

Input Schema

NameRequiredDescriptionDefault
latitudeYesLatitude in decimal degrees, e.g. 43.65 for Toronto.
longitudeYesLongitude in decimal degrees, e.g. -79.38 for Toronto.
maxResultsNoHow many stores to return (1–20).
countryCodeNoOnly return stores in this country.
maxDistanceKmNoLeave out stores farther than this.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.11.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely new behavioral detail: results are sorted nearest-first and carry straight-line distance in km, and storeId feeds downstream tools. It stops short of covering empty-result or out-of-range behavior, so not 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences: what it does, how to call it, what comes back, and where to go next. Every sentence earns its place and the core purpose is front-loaded.

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

Completeness5/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 must describe returns, and it does — ordering, distance units, and the storeId field agents need for chaining. Combined with a fully documented five-parameter schema and clear annotations, nothing an agent needs to call this correctly is missing.

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 100%, so the schema already defines latitude, longitude, maxResults, countryCode, and maxDistanceKm. The description adds meaning beyond it by establishing the precision tolerance for the coordinates, which the schema does not state, and by explaining how the coordinates carry over to sibling tools.

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 ('find the IKEA stores closest to a place') and immediately distinguishes itself from the best-store siblings by naming them. An agent can tell this apart from list_stores or find_best_store_for_item without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent: use the returned storeId values with the stock tools, or pass the same coordinates as `near` to find_best_store_for_item / find_best_store_for_cart. It also pre-empts the common hesitation about coordinate precision by saying an approximate city-centre coordinate is fine.

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