Seemor Restaurant Intelligence

Explore Area

explore_area

Read-onlyIdempotent

Get aggregate dining statistics for a neighborhood, city, or region: cuisine breakdown, grade distribution, price range, top neighborhoods, and highlighted restaurants. Use this for area-level context ("what is the dining scene like in Shoreditch?"), NOT for finding a specific restaurant or getting a personal recommendation. For "find me a quiet Italian near Shoreditch", use the recommend tool instead. Coverage is reported honestly: coverage_level 'full' (fully analyzed rows present), 'basic' (only quick-read rows: review-analysis bands, no letter grades yet), or 'none'; analyzed_count and preliminary_count split total_restaurants, and highlights marked coverage_level 'basic' carry a preliminary_band instead of a grade; the band is the floor of the range, so 'B-range' means at least B minus. not_found means neither analyzed nor preliminary rows exist.

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": {
      "area": "<area>"
    },
    "name": "explore_area"
  }
}

Input Schema

Name	Required	Description	Default
`area`	Yes	Neighborhood, city, or region name, in English or the local language. Supports 'Shoreditch', 'Shoreditch, London', 'Rome' or 'Roma', 'Wien', 'Praha', 'Montréal', 'Chelsea, NYC'. Whenever the conversation shows which place is meant, add its city, state or country after a comma, so a shared name needs no guess; other_places lists the others when a name is shared.

Output Schema

Name	Required	Description	Default
`area`	No
`status`	No
`message`	No
`next_step`	No
`highlights`	No
`place_note`	No
`description`	No
`other_places`	No
`top_cuisines`	No
`neighborhoods`	No
`analyzed_count`	No
`coverage_level`	No
`price_breakdown`	No
`preliminary_count`	No
`total_restaurants`	No
`grade_distribution`	No
`analyzed_restaurants`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 5, 2026
- addedOutput schema / properties / highlights / items / properties / grade_basis
```
Added value: +{
+  "type": "string"
+}
```
Changed1 schema field changedNov 3, 2026
- addedOutput schema / properties / next_step
```
Added value: +{
+  "type": "string"
+}
```
Changed1 schema field changedSep 29, 2026
- addedOutput schema / properties / highlights / items / properties / place_note
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```

Changed1 schema field changedSep 26, 2026

changedInput schema / properties / area / description

Previous value: -"Neighborhood, city, or region name, in English or the local language. Supports 'Shoreditch', 'Shoreditch, London', 'Rome' or 'Roma', 'Wien', 'Praha', 'Montréal', 'Chelsea, NYC'. Use a comma qualifier to pick between places that share a name; other_places lists them when a name is shared."New value: +"Neighborhood, city, or region name, in English or the local language. Supports 'Shoreditch', 'Shoreditch, London', 'Rome' or 'Roma', 'Wien', 'Praha', 'Montréal', 'Chelsea, NYC'. Whenever the conversation shows which place is meant, add its city, state or country after a comma, so a shared name needs no guess; other_places lists the others when a name is shared."

Changed3 schema fields changedSep 25, 2026

changedInput schema / properties / area / description

Previous value: -"Neighborhood, city, or region name. Supports 'Shoreditch', 'Shoreditch, London', 'Central London', 'Rome', 'Chelsea, NYC'. Use comma to disambiguate neighborhoods that exist in multiple cities."New value: +"Neighborhood, city, or region name, in English or the local language. Supports 'Shoreditch', 'Shoreditch, London', 'Rome' or 'Roma', 'Wien', 'Praha', 'Montréal', 'Chelsea, NYC'. Use a comma qualifier to pick between places that share a name; other_places lists them when a name is shared."

addedOutput schema / properties / other_places

Added value: +{
+  "items": {
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / place_note
```
Added value: +{
+  "type": "string"
+}
```

Changed1 schema field changedAug 22, 2026
- changedOutput schema / properties / highlights / items / properties / coverage_level / enum
```
Previous value: -[
-  "full",
-  "basic"
-]New value: +[
+  "full",
+  "basic",
+  "none"
+]
```

Changed6 schema fields changedAug 22, 2026

addedOutput schema / properties / analyzed_count
```
Added value: +{
+  "type": "number"
+}
```

addedOutput schema / properties / coverage_level

Added value: +{
+  "enum": [
+    "full",
+    "basic",
+    "none"
+  ],
+  "type": "string"
+}

changedOutput schema / properties / description / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

addedOutput schema / properties / highlights / items / properties

Added value: +{
+  "address": {
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "caveats": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "city": {
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "coverage_level": {
+    "enum": [
+      "full",
+      "basic"
+    ],
+    "type": "string"
+  },
+  "cuisine_tags": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "distance_km": {
+    "type": [
+      "number",
+      "null"
+    ]
+  },
+  "grade": {
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "name": {
+    "type": "string"
+  },
+  "neighborhood": {
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "preliminary_band": {
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "price_level": {
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "seemor_id": {
+    "type": "string"
+  },
+  "tldr": {
+    "type": [
+      "string",
+      "null"
+    ]
+  }
+}

addedOutput schema / properties / preliminary_count

Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}

addedOutput schema / properties / status / enum

Added value: +[
+  "ok",
+  "error",
+  "not_found"
+]

Changed4 schema fields changedJul 30, 2026
- addedOutput schema / properties / description
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / message
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / neighborhoods
```
Added value: +{
+  "items": {
+    "type": "object"
+  },
+  "type": "array"
+}
```
- addedOutput schema / properties / price_breakdown
```
Added value: +{
+  "type": "object"
+}
```

Changed1 schema field changedJul 6, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "analyzed_restaurants": {
+      "type": "number"
+    },
+    "area": {
+      "type": "string"
+    },
+    "grade_distribution": {
+      "type": "object"
+    },
+    "highlights": {
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "status": {
+      "type": "string"
+    },
+    "top_cuisines": {
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total_restaurants": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

First observedJul 6, 2026

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, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: honest coverage reporting, the full/basic/none levels, the analyzed_count vs preliminary_count split, and the meaning of preliminary_band as the floor of a range. Some of this overlaps the output schema, which keeps it from 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?

Purpose and the use/do-not-use routing are front-loaded in the first two sentences, which is exactly right. The final coverage sentence is long and clause-heavy, packing several distinct concepts into one run-on, which slightly hurts scannability.

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?

For a single-parameter read tool with an output schema and full annotation coverage, the description supplies everything an agent needs: what it returns, when to pick it, which sibling to use instead, and how to interpret partial coverage and not_found 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% and the 'area' parameter already documents accepted formats, multilingual names, and the comma-qualifier convention. The description adds no additional meaning about the parameter, so the baseline 3 applies.

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 ('Get aggregate dining statistics') plus the exact scope (neighborhood, city, region) and enumerates the returned dimensions. It explicitly contrasts with finding a specific restaurant, so an agent can separate it from find_restaurant, lookup_restaurant, and search_restaurants without opening a 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?

Gives an explicit when-to-use example ('what is the dining scene like in Shoreditch?'), an explicit when-not ('NOT for finding a specific restaurant or getting a personal recommendation'), and names the correct alternative ('use the recommend tool instead') with a concrete example query. Nothing is left to inference.

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

All Seemor Restaurant Intelligence tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?