Skip to main content
Glama

Seemor Restaurant Intelligence

Search Restaurants

search_restaurants
Read-onlyIdempotent

Search for restaurants near a place. Name the place with location (for example "Shibuya, Tokyo"), or give its latitude and longitude; one of the two is required, and location wins when both are sent. A name several places share returns status geo_conflict with candidates to choose from, and a name Seemor does not know returns status not_found. 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 or grade_state 'not_highlighted') 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; the band is the floor of the range, so 'B-range' means at least B minus. total_in_area = analyzed_in_area + preliminary_in_area; a message explains when quick-read rows are included. When location names a place Seemor holds, rooms inside that place come first and any room outside it carries a place_note (present it as outside the place asked for); analyzed_in_place counts the analyzed rooms inside and returned_outside_place counts the returned rooms outside.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_restaurants"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoSort order: "grade" (default, best first) or "distance" (nearest first).
limitNoMaximum results to return. Default 10, max 10.
cuisineNoFilter by cuisine type (e.g. "Italian", "Japanese"). Case-insensitive substring match.
latitudeNoLatitude of the place the diner is asking about, as the coordinates of that place (-90 to 90). Do not send the diner's own device location unless the diner gave it.
locationNoName of the place the diner is asking about, e.g. 'Shibuya, Tokyo', 'Soho, London', 'Rome'. Pass it with its city, state or country whenever the conversation shows which place is meant, so a name several places share needs no question. Use this instead of guessing coordinates. Either location or both latitude and longitude is required; if both are sent, location takes priority. This is the place the diner is asking about, named in words; do not fill it from the diner's own device location unless the diner gave it.
longitudeNoLongitude of the place the diner is asking about, as the coordinates of that place (-180 to 180). Do not send the diner's own device location unless the diner gave it.
min_gradeNoMinimum letter grade to include (e.g. "A-"). A minimum leaves out rows Seemor does not highlight; a minimum Seemor cannot apply returns results without a grade filter.
radius_kmNoSearch radius in kilometers. Default 2, max 10.
price_levelNoFilter by price level: "$", "$$", "$$$", or "$$$$".

Output Schema

NameRequiredDescriptionDefault
statusNo
messageNo
resultsNo
next_stepNo
candidatesNo
place_noteNo
ai_generatedNo
other_placesNo
location_usedNo
total_in_areaNo
more_candidatesNo
analyzed_in_areaNo
query_understoodNo
total_candidatesNo
analyzed_in_placeNo
digital_source_typeNo
preliminary_in_areaNo
returned_outside_placeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / min_grade / description
      Previous value: -"Minimum letter grade to include (e.g. \"B+\"). Grades: A+, A, A-, B+, B, B-, C+, C, C-, D, F."New value: +"Minimum letter grade to include (e.g. \"A-\"). A minimum leaves out rows Seemor does not highlight; a minimum Seemor cannot apply returns results without a grade filter."
    • addedOutput schema / properties / ai_generated
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / digital_source_type
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / results / items / properties / grade_label
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / results / items / properties / grade_state
      Added value: +{
      +  "enum": [
      +    "not_highlighted"
      +  ],
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • addedOutput schema / properties / results / items / properties / grade_basis
      Added value: +{
      +  "type": "string"
      +}
  3. Changed15 schema fields changed
    • changedInput schema / properties / latitude / description
      Previous value: -"Latitude of the search center (-90 to 90)."New value: +"Latitude of the place the diner is asking about, as the coordinates of that place (-90 to 90). Do not send the diner's own device location unless the diner gave it."
    • addedInput schema / properties / location
      Added value: +{
      +  "description": "Name of the place the diner is asking about, e.g. 'Shibuya, Tokyo', 'Soho, London', 'Rome'. Pass it with its city, state or country whenever the conversation shows which place is meant, so a name several places share needs no question. Use this instead of guessing coordinates. Either location or both latitude and longitude is required; if both are sent, location takes priority. This is the place the diner is asking about, named in words; do not fill it from the diner's own device location unless the diner gave it.",
      +  "type": "string"
      +}
    • changedInput schema / properties / longitude / description
      Previous value: -"Longitude of the search center (-180 to 180)."New value: +"Longitude of the place the diner is asking about, as the coordinates of that place (-180 to 180). Do not send the diner's own device location unless the diner gave it."
    • changedInput schema / required
      Previous value: -[
      -  "latitude",
      -  "longitude"
      -]New value: +[]
    • addedOutput schema / properties / analyzed_in_place
      Added value: +{
      +  "type": "number"
      +}
    • addedOutput schema / properties / candidates
      Added value: +{
      +  "items": {
      +    "properties": {
      +      "city": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "country": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "label": {
      +        "type": "string"
      +      },
      +      "lat": {
      +        "type": "number"
      +      },
      +      "lng": {
      +        "type": "number"
      +      }
      +    },
      +    "type": "object"
      +  },
      +  "type": [
      +    "array",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / location_used
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / more_candidates
      Added value: +{
      +  "type": "number"
      +}
    • addedOutput schema / properties / next_step
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / other_places
      Added value: +{
      +  "items": {
      +    "properties": {
      +      "city": {
      +        "type": "string"
      +      },
      +      "country": {
      +        "type": "string"
      +      },
      +      "label": {
      +        "type": "string"
      +      },
      +      "name": {
      +        "type": "string"
      +      }
      +    },
      +    "type": "object"
      +  },
      +  "type": [
      +    "array",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / place_note
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / query_understood
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / results / items / properties / place_note
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / returned_outside_place
      Added value: +{
      +  "type": "number"
      +}
    • addedOutput schema / properties / total_candidates
      Added value: +{
      +  "type": "number"
      +}
  4. Changed1 schema field changed
    • changedOutput schema / properties / results / items / properties / coverage_level / enum
      Previous value: -[
      -  "full",
      -  "basic"
      -]New value: +[
      +  "full",
      +  "basic",
      +  "none"
      +]
  5. Changed12 schema fields changed
    • 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"
      +  ]
      +}
  6. Changed3 schema fields changed
    • 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"
      +}
  7. Changed1 schema field changed
    • 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"
      +}
  8. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), yet the description adds substantial behavior: geo_conflict and not_found statuses for unresolvable or ambiguous place names, ordered ranking of full vs quick-read restaurants, the meaning of coverage_level, grade_state and preliminary_band, and a place_note for rooms outside the requested place. That is far beyond what the structured fields convey.

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?

Purpose and the recommend alternative are front-loaded, which is good, but the final paragraph is a long run-on covering coverage_level, bands, counters and place_note in one breath. The location-versus-coordinates requirement is stated twice, duplicating schema text rather than earning its place.

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?

Despite nine parameters and an output schema (so return shape needn't be re-explained), the description covers what an agent must know to call and interpret it: input precedence, ambiguity handling, result ordering, the meaning of quick-read rows, and how to present out-of-place results. Nothing needed for correct invocation is missing.

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 coverage is 100%, so the baseline is 3 and the schema already documents every parameter including the location-over-coordinates priority. The description reinforces the place-vs-device-location distinction and adds the geo_conflict consequence of an ambiguous name, but adds little syntax or format meaning beyond 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 first sentence states a specific verb and resource ("Search for restaurants near a place") and the description immediately scopes it ("browsing a list by distance or filters"), explicitly contrasting it with recommend. An agent can distinguish it from recommend without opening either 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?

It names the alternative tool and the condition that selects it: recommendations or picking where to eat go to recommend, list browsing by distance or filters stays here. It also gives routing rules for the required input (location vs coordinates, location wins) so the agent knows how to invoke it in ambiguous cases.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources