Dim Hour

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

Name	Required	Description
`city`	Yes	City name or key from list_cities
`limit`	No	Max results, default 6
`max_price`	No	Max price tier 1-4
`looking_for`	No	What the occasion needs, e.g. 'omakase', 'patio', 'birthday dinner'
`neighborhood`	No	Narrow to a neighborhood

Output Schema

Name	Required	Description	Default
`city`	Yes
`note`	No
`venues`	Yes
`receipt`	Yes
`showing`	Yes
`total_matches`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 3, 2026
- addedOutput schema / properties / receipt / properties / scope_note
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
AddedSep 17, 2026

TDQS

A4.3/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 safety and closed-world scoping are covered structurally. The description confirms the single-city scope and adds that results are 'ranked, citable venues with a freshness receipt', which is useful signal about output character, though an output schema exists so return details are largely redundant.

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?

Two sentences, front-loaded with the purpose before the sibling routing. Slightly jargon-laden phrases ('task-shaped entry point', 'freshness receipt') cost a bit of clarity but carry real meaning.

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?

Annotations cover the safety profile, an output schema covers the return values, and the schema documents all five parameters, so the description only needs to establish purpose and routing — which it does. Minor gaps, such as default result count or behavior when filters yield nothing, are left entirely to the schema.

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 earns one extra point by mapping natural-language occasion needs ('a cuisine, a neighborhood, a budget, a vibe') onto the specific inputs, which helps an agent decide how to compose looking_for, neighborhood and max_price together rather than treat them as isolated fields.

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 ('Find places'), plus explicit scope: one city, one occasion. It also labels itself 'the task-shaped entry point', which tells an agent this is the top-level entry rather than a lookup, distinguishing it from get_venue or search_venues.

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 a positive use case ('use it to plan an outing') and names the alternative with its differentiating condition ('use search_venues to browse'). The agent does not have to infer which of the two siblings to pick.

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

All Dim Hour 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?