Seemor Restaurant Intelligence

Search Restaurants

search_restaurants

Read-onlyIdempotent

Search for restaurants near a location. For picking where to eat or giving recommendations, use recommend; this tool is for browsing a list by distance or filters. Returns graded, ranked results with cuisine, price level, and Seemor analysis summaries. Fully analyzed restaurants (coverage_level 'full', letter grade) come first; when fewer than limit are available, quick-read restaurants are appended after them, marked coverage_level 'basic' with grade null and a preliminary_band (e.g. 'A-range') graded from review analysis, not star ratings. total_in_area = analyzed_in_area + preliminary_in_area; a message explains when quick-read rows are included.

Input Schema

TableJSON Schema

Name	Required	Description
`sort`	No	Sort order: "grade" (default, best first) or "distance" (nearest first).
`limit`	No	Maximum results to return. Default 10, max 10.
`cuisine`	No	Filter by cuisine type (e.g. "Italian", "Japanese"). Case-insensitive substring match.
`latitude`	Yes	Latitude of the search center (-90 to 90).
`longitude`	Yes	Longitude of the search center (-180 to 180).
`min_grade`	No	Minimum letter grade to include (e.g. "B+"). Grades: A+, A, A-, B+, B, B-, C+, C, C-, D, F.
`radius_km`	No	Search radius in kilometers. Default 2, max 10.
`price_level`	No	Filter by price level: "$", "$$", "$$$", or "$$$$".

Output Schema

TableJSON Schema

Name	Required	Description	Default
`status`	No
`message`	No
`results`	No
`total_in_area`	No
`analyzed_in_area`	No
`preliminary_in_area`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 22, 2026
- changedOutput schema / properties / results / items / properties / coverage_level / enum
```
Previous value: -[
-  "full",
-  "basic"
-]New value: +[
+  "full",
+  "basic",
+  "none"
+]
```
Changed12 schema fields changedAug 22, 2026
- addedOutput schema / properties / analyzed_in_area
```
Added value: +{
+  "type": "number"
+}
```
- addedOutput schema / properties / preliminary_in_area
```
Added value: +{
+  "type": "number"
+}
```
- changedOutput schema / properties / results / items / properties / address / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- addedOutput schema / properties / results / items / properties / caveats
```
Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
```
- changedOutput schema / properties / results / items / properties / city / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- addedOutput schema / properties / results / items / properties / coverage_level / enum
```
Added value: +[
+  "full",
+  "basic"
+]
```
- addedOutput schema / properties / results / items / properties / distance_km
```
Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
```
- changedOutput schema / properties / results / items / properties / grade / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / results / items / properties / neighborhood / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- addedOutput schema / properties / results / items / properties / preliminary_band
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / results / items / properties / price_level
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / results / items / properties / tldr
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
Changed3 schema fields changedJul 30, 2026
- addedOutput schema / properties / message
```
Added value: +{
+  "type": "string"
+}
```
- removedOutput schema / properties / total
```
Removed value: -{
-  "type": "number"
-}
```
- addedOutput schema / properties / total_in_area
```
Added value: +{
+  "type": "number"
+}
```

Changed1 schema field changedJul 6, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "results": {
+      "items": {
+        "properties": {
+          "address": {
+            "type": "string"
+          },
+          "city": {
+            "type": "string"
+          },
+          "coverage_level": {
+            "type": "string"
+          },
+          "cuisine_tags": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "grade": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "neighborhood": {
+            "type": "string"
+          },
+          "seemor_id": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "status": {
+      "type": "string"
+    },
+    "total": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

First observedJul 6, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Although annotations already declare readOnlyHint=true and idempotentHint=true, the description adds substantial behavioral detail: result ranking (fully analyzed first, quick-read appended), coverage_level values ('full' vs 'basic'), grade null with preliminary_band, the formula total_in_area = analyzed_in_area + preliminary_in_area, and the message explaining quick-read inclusion. This goes well beyond the annotations and tells the agent exactly how results are composed.

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 description is front-loaded with purpose and alternative, then builds out behavioral details in a logical order. Every sentence carries distinct information—core purpose, sibling routing, return characteristics, ranking logic, and area count formula—with no redundancy or filler.

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?

The output schema covers return values, and annotations cover safety. The description supplies everything an agent needs for correct invocation: when to use it, what it returns, how results are ordered and labeled, and when quick-read rows appear. No critical gaps remain.

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 baseline is 3. The description adds value by clarifying the `limit` parameter's effect on result composition ('when fewer than `limit` are available, quick-read restaurants are appended after them'), which is not in the schema. It also references filters generically, but does not need to repeat 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+resource ('Search for restaurants near a location') and immediately differentiates this tool from the sibling 'recommend' by stating 'this tool is for browsing a list by distance or filters.' This gives an agent a clear, distinct role and prevents confusion with sibling tools.

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?

It explicitly says 'For picking where to eat or giving recommendations, use recommend; this tool is for browsing a list by distance or filters.' This names the alternative, states the condition for choosing this tool, and implicitly excludes single-lookup usage. The guidance is direct and actionable.

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?