Seemor Restaurant Intelligence

Look Up Restaurant

lookup_restaurant

Read-onlyIdempotent

Look up a specific restaurant by its Seemor ID. Returns grade, summary, cuisine, neighborhood, and other details. Use the fields parameter to request richer data (standard or premium; fully analyzed restaurants only, except the quick-read dimension_assessments below). coverage_level 'full' rows carry a letter grade (or grade_state 'not_highlighted' with grade null); 'basic' rows are Seemor quick reads: review-analysis bands (grade null, preliminary_band such as 'B-range') with a one-line tldr, graded from review analysis rather than star ratings; the band is the floor of the range, so 'B-range' means at least B minus. With fields 'premium' a quick-read row also carries dimension_assessments for the dimensions the quick read measured (food quality, consistency, noise, service attentiveness, large parties, local vs tourist, value), labelled on the same scale as full analysis but read from fewer reviews, so present them as preliminary. 'none' rows have no analysis yet. Rows carry google_maps_url and website when Seemor holds them (null otherwise), plus seemor_url. Seemor holds no booking, availability or opening-hours data: use a booking app for those and join on restaurant name and address. Use search_restaurants or find_restaurant first to get restaurant IDs. Use this for a single place the user asks about, not for every result of recommend.

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": {
      "restaurant_id": "<restaurant_id>"
    },
    "name": "lookup_restaurant"
  }
}

Input Schema

Name	Required	Description	Default
`fields`	No	Response detail level. 'basic' (default): grade, TL;DR, cuisine, price. 'standard': adds narrative summary, occasion fit, menu highlights, cost estimates, dietary info. 'premium': adds dimensional assessments (noise, formality, authenticity, etc.), value assessment, standout strengths/weaknesses, unique selling points.
`restaurant_id`	Yes	Seemor restaurant ID (UUID). Get IDs from search_restaurants results.

Output Schema

Name	Required	Description	Default
`status`	No
`message`	No
`next_step`	No
`restaurant`	No
`ai_generated`	No
`digital_source_type`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 10, 2026
- addedOutput schema / properties / ai_generated
```
Added value: +{
+  "type": "boolean"
+}
```
- addedOutput schema / properties / digital_source_type
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / restaurant / properties / grade_state
```
Added value: +{
+  "enum": [
+    "not_highlighted"
+  ],
+  "type": "string"
+}
```
Changed1 schema field changedNov 5, 2026
- addedOutput schema / properties / restaurant / properties / grade_basis
```
Added value: +{
+  "type": "string"
+}
```
Changed3 schema fields changedNov 3, 2026
- addedOutput schema / properties / next_step
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / restaurant / properties / google_maps_url
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / restaurant / properties / website
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
Changed8 schema fields changedAug 22, 2026
- addedOutput schema / properties / message
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / restaurant / properties / address
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / restaurant / properties / analysis_date
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / restaurant / properties / caveats
```
Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
```
- addedOutput schema / properties / restaurant / properties / city
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / restaurant / properties / coverage_level
```
Added value: +{
+  "enum": [
+    "full",
+    "basic",
+    "none"
+  ],
+  "type": "string"
+}
```
- addedOutput schema / properties / restaurant / properties / preliminary_band
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / restaurant / properties / seemor_url
```
Added value: +{
+  "type": "string"
+}
```
Changed5 schema fields changedAug 22, 2026
- changedOutput schema / properties / restaurant / properties / grade / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / restaurant / properties / grade_label / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / restaurant / properties / neighborhood / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / restaurant / properties / price_level / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / restaurant / properties / tldr / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```

Changed1 schema field changedJul 13, 2026

changedInput schema / properties / fields / description

Previous value: -"Response detail level. 'basic' (default): grade, TL;DR, cuisine, price. 'standard': adds narrative summary, occasion fit, menu highlights, cost estimates, dietary info. 'premium': adds dimensional scores (noise, formality, authenticity, etc.), value assessment, strengths/weaknesses."New value: +"Response detail level. 'basic' (default): grade, TL;DR, cuisine, price. 'standard': adds narrative summary, occasion fit, menu highlights, cost estimates, dietary info. 'premium': adds dimensional assessments (noise, formality, authenticity, etc.), value assessment, standout strengths/weaknesses, unique selling points."

Changed1 schema field changedJul 6, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "restaurant": {
+      "properties": {
+        "cuisine_tags": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "grade": {
+          "type": "string"
+        },
+        "grade_label": {
+          "type": "string"
+        },
+        "name": {
+          "type": "string"
+        },
+        "neighborhood": {
+          "type": "string"
+        },
+        "price_level": {
+          "type": "string"
+        },
+        "seemor_id": {
+          "type": "string"
+        },
+        "tldr": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "status": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedJul 6, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations only cover the read-only/idempotent safety profile, yet the description discloses far more: coverage_level semantics ('full' rows graded, 'basic' rows are preliminary bands floored at the range minimum, 'none' rows unanalyzed), the meaning of grade null plus grade_state 'not_highlighted', and null-vs-populated behavior for google_maps_url and website. It also flags that quick-read dimension_assessments come from fewer reviews and should be presented as preliminary, which is genuine interpretation guidance an agent could not infer from annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The purpose and the sibling routing are correctly front-loaded, but the body is a single very dense paragraph with stacked parentheticals and parenthesized enum values that make it slow to parse. Nearly every sentence carries information, yet the same coverage/grade rules could be stated in fewer, shorter sentences.

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 2-parameter lookup with an output schema, this covers everything an agent needs: how to get the ID, what each fields level does, how to read coverage_level and band labels, what is null, and what data the backend simply does not have. Nothing material is left for the agent to guess.

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 real value by explaining how 'premium' behaves on quick-read rows and by naming the specific quick-read dimensions, which the schema only describes generically ('noise, formality, authenticity, etc.'). The dimension lists in description and schema do not fully agree (food quality/consistency/large parties/local vs tourist vs formality/authenticity), which slightly muddies rather than clarifies.

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 ('look up a specific restaurant by its Seemor ID') and enumerates the returned fields (grade, summary, cuisine, neighborhood). It also distinguishes itself from siblings by naming search_restaurants and find_restaurant as the ID-discovery path and recommend as a different use case.

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 says to call search_restaurants or find_restaurant first to obtain IDs, and states 'Use this for a single place the user asks about, not for every result of recommend' — a clear when-not rule tied to a named sibling. It also sets a boundary on out-of-scope needs ('Seemor holds no booking, availability or opening-hours data: use a booking app').

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?