Dim Hour

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. Prefer this over search_venues when you are planning rather than browsing.

Input Schema

TableJSON 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

TableJSON 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.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context beyond them: results are ranked, citable, and come with a 'freshness receipt'. It does not discuss rate limits or failure modes, keeping it short of a 5.

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?

Three tight sentences, front-loaded with the core action and scope, followed by inputs and then the sibling-routing rule. No sentence is redundant.

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?

An output schema exists, so return values need not be explained, and annotations carry the safety profile. What remains - what the tool does, what to pass, and when to prefer it over the sibling - is all present.

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 description coverage is 100%, so all five parameters are already documented, making 3 the baseline. The description loosely maps the occasion needs to inputs ('a cuisine, a neighborhood, a budget, a vibe') but adds no syntax or format detail 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?

States a specific verb+resource (find places) plus the scope constraint 'in one city', and explicitly labels itself the task-shaped entry point. It distinguishes itself from the sibling search_venues by name, so an agent can route 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?

Gives an explicit selection rule: 'Prefer this over search_venues when you are planning rather than browsing.' That names the alternative and the condition that chooses it, which is exactly what routing guidance should do.

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?