Seemor Restaurant Intelligence

Get Recommendations

recommend

Read-only

Returns a complete, ranked restaurant recommendation for a dining occasion: the final answer, not a search. Each result already carries a grade (or preliminary_band), match_reasons, and caveats weighed against the request. Call it ONCE per question, with the full ask (cuisine, occasion, vibe, constraints) in query and the place in location. Do not re-call with reworded variations or call lookup_restaurant on each result to double-check it; that adds latency, not a better answer. If a result carries caveats, coverage_level 'basic', or a message noting a thin pool, relay it to the user instead of searching again. Requires a location: include one in your query (e.g. "in Soho"), or provide location, or latitude/longitude, or the tool refuses with location_required instead of guessing a city.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Number of recommendations to return (1-10, default 5).
`query`	Yes	Natural language dining request, e.g. 'quiet Italian restaurant for a date night in Covent Garden' or 'best sushi near me for a celebration'. Include the location in your query OR provide latitude/longitude.
`latitude`	No	Latitude of search center. Alternative to location — use when you have coordinates. If both location and lat/lng are provided, location takes priority for disambiguation.
`location`	No	City or area to bias the search toward, e.g. 'London', 'San Francisco', 'Rome'. Use this when the query doesn't include a location, or to disambiguate (e.g. 'Victoria' could be London or British Columbia — pass 'London' to clarify). If omitted and the query contains a location, that location is used.
`longitude`	No	Longitude of search center. Must be provided with latitude.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`status`	No
`message`	No
`results`	No
`location_used`	No
`pool_disclosure`	No
`query_understood`	No
`total_candidates`	No
`unverifiable_attributes`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed3 schema fields changedAug 30, 2026

addedOutput schema / properties / pool_disclosure

Added value: +{
+  "properties": {
+    "count": {
+      "type": "number"
+    },
+    "message": {
+      "type": "string"
+    },
+    "reason": {
+      "enum": [
+        "thin_pool",
+        "cuisine_relaxed"
+      ],
+      "type": "string"
+    }
+  },
+  "type": [
+    "object",
+    "null"
+  ]
+}

changedOutput schema / properties / status / enum

Previous value: -[
-  "ok",
-  "error",
-  "no_coverage",
-  "location_required",
-  "timeout"
-]New value: +[
+  "ok",
+  "error",
+  "no_coverage",
+  "location_required",
+  "timeout",
+  "cannot_verify"
+]

addedOutput schema / properties / unverifiable_attributes

Added value: +{
+  "items": {
+    "properties": {
+      "key": {
+        "type": "string"
+      },
+      "label": {
+        "type": "string"
+      },
+      "source_phrase": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": [
+    "array",
+    "null"
+  ]
+}

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

Changed4 schema fields changedAug 22, 2026

addedOutput schema / properties / results / items / properties / coverage_level

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

changedOutput schema / properties / results / items / properties / grade / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
addedOutput schema / properties / results / items / properties / preliminary_band
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```

changedOutput schema / properties / status / enum

Previous value: -[
-  "ok",
-  "error",
-  "no_coverage",
-  "location_required"
-]New value: +[
+  "ok",
+  "error",
+  "no_coverage",
+  "location_required",
+  "timeout"
+]

Changed1 schema field changedAug 21, 2026
- addedOutput schema / properties / results / items / properties / caveats
```
Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
```

Changed7 schema fields changedJul 30, 2026

addedOutput schema / properties / location_used
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / message
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / query_understood
```
Added value: +{
+  "type": "string"
+}
```

removedOutput schema / properties / recommendations

Removed value: -{
-  "items": {
-    "properties": {
-      "grade": {
-        "type": "string"
-      },
-      "match_reasons": {
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      },
-      "name": {
-        "type": "string"
-      },
-      "relevance": {
-        "type": "string"
-      },
-      "seemor_id": {
-        "type": "string"
-      }
-    },
-    "type": "object"
-  },
-  "type": "array"
-}

addedOutput schema / properties / results

Added value: +{
+  "items": {
+    "properties": {
+      "distance_km": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "grade": {
+        "type": "string"
+      },
+      "match_reasons": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "name": {
+        "type": "string"
+      },
+      "relevance": {
+        "type": "string"
+      },
+      "seemor_id": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / status / enum

Added value: +[
+  "ok",
+  "error",
+  "no_coverage",
+  "location_required"
+]

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

Changed1 schema field changedJul 6, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "recommendations": {
+      "items": {
+        "properties": {
+          "grade": {
+            "type": "string"
+          },
+          "match_reasons": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "name": {
+            "type": "string"
+          },
+          "relevance": {
+            "type": "string"
+          },
+          "seemor_id": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "status": {
+      "type": "string"
+    }
+  },
+  "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?

Annotations already establish read-only, non-destructive behavior, and the description adds meaningful context: results are pre-scored with grades and caveats, re-calling only 'adds latency, not a better answer', and missing location causes a location_required refusal instead of a guessed city. No contradiction with the annotations.

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 main purpose is front-loaded in the first sentence, and each subsequent sentence carries distinct usage or behavioral guidance. The length is warranted by the number of common misuse patterns the description proactively prevents, with no 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?

Combined with the output schema and annotations, the description covers everything needed for correct invocation: call budget, query and location relationship, error mode, and how to handle low-confidence or caveated results. Nothing essential is left implicit.

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 schema already documents all five parameters with full coverage, so the baseline is 3. The description adds value by defining the query as the full ask and clarifying the location requirement and refusal behavior, while leaving limit and coordinate details to 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?

Opens with a precise deliverable: 'Returns a complete, ranked restaurant recommendation for a dining occasion: the final answer, not a search.' This clearly distinguishes the tool from search and lookup siblings, and tells the agent this is the final recommendation rather than a list of candidates.

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 explicit when and how to use it: call once per question with the full ask, include the place in location, and do not re-call with reworded variations. It also explicitly warns against calling lookup_restaurant to double-check results and instructs relaying caveats instead of searching again, which directly handles the likely alternatives.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation4/5

Most tools are clearly distinct: find_restaurant searches by name, search_restaurants searches by location, explore_area gives area statistics, and recommend gives a final ranked recommendation. Some minor overlap exists between lookup_restaurant and ask_about_restaurant and between search_restaurants and recommend, but the descriptions carefully separate structured details from Q&A and search from final recommendations.

Naming Consistency4/5

Tool names mostly follow a clear verb_noun pattern: find_restaurant, lookup_restaurant, search_restaurants, explore_area, and ask_about_restaurant. The exception is recommend, which is a bare verb with no object, creating a minor inconsistency but not enough to cause confusion.

Tool Count5/5

Six tools is well-scoped for a restaurant intelligence server, covering discovery, lookup, area exploration, Q&A, and recommendations. Each tool earns its place and there is no bloat or redundancy.

Completeness5/5

The tool surface covers the full workflow: find or search restaurants, look up details, ask specific questions, explore area context, and get a final recommendation. There are no obvious dead ends, and the tool descriptions explicitly explain how IDs flow from one tool to another.

Resources

Need Help?