Skip to main content
Glama
This connector has been deprecated

Superseded by the canonical Dim Hour connector at https://glama.ai/mcp/connectors/com.dimhour.mcp/dim-hour (same server on its branded domain).

Find places

find_places
Read-only

Find places for a specific occasion in one city — the task-shaped entry point. Give the city and what the evening needs (a cuisine, a neighborhood, a budget, a vibe) and it returns ranked, citable venues with a freshness receipt. Use it to plan an outing; use search_venues to browse.

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": {
      "city": "<city>"
    },
    "name": "find_places"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesCity name or key from list_cities
limitNoMax results, default 6
max_priceNoMax price tier 1-4
looking_forNoWhat the occasion needs, e.g. 'omakase', 'patio', 'birthday dinner'
neighborhoodNoNarrow to a neighborhood

Output Schema

NameRequiredDescriptionDefault
cityYes
noteNo
venuesYes
receiptYes
showingYes
total_matchesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedOutput schema / properties / receipt / properties / age_days
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • removedOutput schema / properties / receipt / properties / stale
      Removed value: -{
      -  "type": "boolean"
      -}
    • changedOutput schema / properties / receipt / required
      Previous value: -[
      -  "as_of",
      -  "as_of_scope",
      -  "source",
      -  "abstained",
      -  "stale",
      -  "reason"
      -]New value: +[
      +  "as_of",
      +  "as_of_scope",
      +  "source",
      +  "abstained",
      +  "age_days",
      +  "reason"
      +]
  2. Changed1 schema field changed
    • addedOutput schema / properties / receipt / properties / scope_note
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  3. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the result character — "ranked, citable venues with a freshness receipt" — which is useful behavioral color, but with an output schema present that information is partly redundant, and nothing is said about pagination, limits, or what happens when a city has no matches.

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?

Three tight sentences with the scope front-loaded before the alternative is named; nothing is wasted. The phrase "task-shaped entry point" is slight jargon an agent doesn't strictly need, which keeps it just short of ideal.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With one required parameter, full schema coverage, an output schema and mutation-free annotations, the description covers the role and routing decisions an agent needs. The remaining gap is thinness around degenerate cases (no matches, result limits) rather than any missing core information.

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 every one of the five parameters is already documented in the schema; the baseline of 3 applies. The description loosely restates four of them (cuisine, neighborhood, budget, vibe) and frames "looking_for" as the evening's need, but adds no format or edge-case detail beyond the schema's own examples.

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 uses a specific verb plus resource ("Find places"), pins the scope to a single city and a specific occasion, and self-describes as the "task-shaped entry point." It explicitly distinguishes itself from search_venues, so an agent can tell the two apart without opening the schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear when-to-use rule ("Use it to plan an outing") and names the alternative with its own condition ("use search_venues to browse"). The contrast is real but thin — "browse" is not defined, and there are no explicit exclusions such as when not to use it or prerequisites.

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