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).

List new venues

list_new_venues
Read-only

Venues recently added to the Dim Hour catalog — across all 26 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.

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": "list_new_venues"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoOptional city name or key; omit for all cities
daysNoLook-back window in days, default 30 (max 90)
limitNoMax results, default 25

Output Schema

NameRequiredDescriptionDefault
cityYes
venuesYes
receiptYes
showingYes
total_newYes
window_daysYes
feed_generatedNo

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. Changed2 schema fields changed
    • addedOutput schema / properties / receipt
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "abstained": {
      +      "type": "boolean"
      +    },
      +    "as_of": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "as_of_scope": {
      +      "type": "string"
      +    },
      +    "reason": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "source": {
      +      "type": "string"
      +    },
      +    "stale": {
      +      "type": "boolean"
      +    }
      +  },
      +  "required": [
      +    "as_of",
      +    "as_of_scope",
      +    "source",
      +    "abstained",
      +    "stale",
      +    "reason"
      +  ],
      +  "type": "object"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "window_days",
      -  "city",
      -  "total_new",
      -  "showing",
      -  "venues"
      -]New value: +[
      +  "window_days",
      +  "city",
      +  "total_new",
      +  "showing",
      +  "receipt",
      +  "venues"
      +]
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "city": {
      +      "type": "string"
      +    },
      +    "feed_generated": {
      +      "type": "string"
      +    },
      +    "showing": {
      +      "type": "number"
      +    },
      +    "total_new": {
      +      "type": "number"
      +    },
      +    "venues": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "awards": {
      +            "type": "string"
      +          },
      +          "city": {
      +            "type": "string"
      +          },
      +          "city_name": {
      +            "type": "string"
      +          },
      +          "cuisine": {
      +            "type": "string"
      +          },
      +          "estimated": {
      +            "type": "boolean"
      +          },
      +          "first_seen": {
      +            "type": "string"
      +          },
      +          "happy_hour": {
      +            "type": "string"
      +          },
      +          "id": {
      +            "type": "number"
      +          },
      +          "name": {
      +            "type": "string"
      +          },
      +          "neighborhood": {
      +            "type": "string"
      +          },
      +          "price": {
      +            "type": "string"
      +          },
      +          "score": {
      +            "type": "number"
      +          },
      +          "url": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "city",
      +          "city_name",
      +          "id",
      +          "name",
      +          "cuisine",
      +          "neighborhood",
      +          "awards",
      +          "happy_hour",
      +          "first_seen",
      +          "url"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "window_days": {
      +      "type": "number"
      +    }
      +  },
      +  "required": [
      +    "window_days",
      +    "city",
      +    "total_new",
      +    "showing",
      +    "venues"
      +  ],
      +  "type": "object"
      +}
  5. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description goes further by disclosing result composition and ordering: scored food/drink venues come first, then unscored hotels, malls, museums and landmarks, with recency ordering within each group. It also flags a real data-quality caveat — dates before 2026-06-06 are reconstructed estimates — which the agent could not know from structured fields. It does not mention auth or rate limits, 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?

Four sentences, each front-loaded with a distinct payload: scope, use cases, ordering/composition, then the date caveat. No sentence repeats the title or the schema, and the most decision-relevant information (what it returns and how it is ordered) appears before the caveat.

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; the description fills the remaining gaps — result grouping, ordering rule, scope across cities, and data-provenance caveat. For a three-optional-parameter read tool this is sufficient to call it 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 coverage is 100%, so all three parameters are already documented with types, ranges and defaults, making 3 the baseline. The description adds only indirect context ('all 26 cities' implying the cardinality of the city dimension); days and limit semantics come entirely from the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Venues recently added to the Dim Hour catalog') plus scope ('across all 26 cities or one city'), which is far more than the title restates. It does not explicitly name a contrasting sibling like search_venues, so differentiation is inferred from the 'recently added' framing rather than stated.

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?

Gives concrete use cases — 'what's new on Dim Hour', new-opening alerts, weekly digests — which is clear when-to-use guidance an agent can match against intent. It stops short of exclusions or naming an alternative for non-recency venue lookups, so there is no when-not clause.

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