Dim Hour

List new venues

list_new_venues

Read-only

Venues recently added to the Dim Hour catalog — across all 24 cities or one city. Use for 'what's new on Dim Hour' / new-opening alerts / weekly digests. Scored places to eat and drink come first; hotels, malls, museums and landmarks carry no score and follow them. Recency orders within each group. Dates earlier than 2026-06-06 are estimates reconstructed from history.

Input Schema

TableJSON Schema

Name	Required	Description
`city`	No	Optional city name or key; omit for all cities
`days`	No	Look-back window in days, default 30 (max 90)
`limit`	No	Max results, default 25

Output Schema

TableJSON Schema

Name	Required	Description	Default
`city`	Yes
`venues`	Yes
`showing`	Yes
`total_new`	Yes
`window_days`	Yes
`feed_generated`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedSep 6, 2026

TDQS

A4.5/5.0

Behavior5/5

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

With readOnlyHint and destructiveHint annotations already covering safety, the description adds valuable behavioral detail: scoring affects ordering, non-scored venue types are grouped after scored ones, ordering is by recency within groups, and pre-2026-06-06 dates are estimates. These are exactly the kind of non-obvious behaviors an agent needs to interpret results correctly.

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?

The description is compact and well-organized: purpose first, then use cases, then result ordering, then the date-estimate caveat. Every sentence carries meaningful information with no filler or redundancy.

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?

The description covers what the tool does, when to use it, how results are ordered and grouped, and the key data-quality caveat about estimated dates. Combined with a complete input schema and an output schema, nothing essential is missing for an agent to select and invoke this tool correctly.

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 the schema already documents city, days, and limit. The description reinforces the city scope ('across all 24 cities or one city') but adds no new parameter-level meaning beyond the schema baseline.

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 states a specific verb and resource: listing venues recently added to the Dim Hour catalog, with a clear scope of all 24 cities or one city. The phrase 'recently added' cleanly distinguishes it from sibling tools like search or list_curated without needing to open their 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 explicitly names concrete use cases: 'what's new on Dim Hour', new-opening alerts, and weekly digests. It does not provide exclusion criteria or directly reference alternatives, but the stated use cases give an agent clear context for when this tool is appropriate.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0

Disambiguation2/5

fetch and get_venue both retrieve essentially the same full venue record, differing only by an extra long-form story field. Similarly, search and search_venues both search the same catalog and return ranked venue results, making it unclear which one an agent should call and creating real misselection risk.

Naming Consistency3/5

The list_* tools are consistent and readable, and most tools use snake_case verb_noun naming. However, fetch and search are bare verbs, and fetch vs get_venue introduces two different verbs for the same operation, so the overall pattern is mixed but still understandable.

Tool Count4/5

Seven tools is a reasonable size for a venue guide server, but the count is slightly padded because fetch duplicates get_venue and search duplicates search_venues. The effective surface is closer to five distinct tools, so the count is slightly over what is needed.

Completeness4/5

The read-only domain is well covered: city discovery, search, curated editorial lists, new venue updates, and full venue details are all present, and search naturally leads into detail retrieval. Minor gaps exist, such as no dedicated non-search way to browse all venues in a city, but the core workflows have no dead ends.

Resources

Need Help?