list_curatedDim Hour's editorial themed lists for a city (e.g. 'Unmarked Doors' speakeasies). Without list_id: returns all list titles. With list_id: returns that list's venues with editorial notes.
| Name | Required | Description | Default |
|---|---|---|---|
| city | Yes | City name or key | |
| list_id | No | A list id from the no-arg call |
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | ||
| city | Yes | ||
| note | No | ||
| lists | No | ||
| title | No | ||
| venues | No | ||
| subtitle | No |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Output schema / (root)Previous value: -nullNew value: +{
+ "$schema": "http://json-schema.org/draft-07/schema#",
+ "additionalProperties": false,
+ "properties": {
+ "city": {
+ "type": "string"
+ },
+ "id": {
+ "type": "string"
+ },
+ "lists": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "id": {
+ "type": "string"
+ },
+ "subtitle": {
+ "type": "string"
+ },
+ "title": {
+ "type": "string"
+ },
+ "venue_count": {
+ "type": "number"
+ }
+ },
+ "required": [
+ "id",
+ "title",
+ "subtitle",
+ "venue_count"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "note": {
+ "type": "string"
+ },
+ "subtitle": {
+ "type": "string"
+ },
+ "title": {
+ "type": "string"
+ },
+ "venues": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "id": {
+ "type": "number"
+ },
+ "name": {
+ "type": "string"
+ },
+ "neighborhood": {
+ "type": "string"
+ },
+ "note": {
+ "type": "string"
+ },
+ "price": {
+ "type": "string"
+ },
+ "url": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "id",
+ "note",
+ "url"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "city"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds meaningful behavioral detail beyond annotations: the response differs based on whether list_id is supplied, returning list titles in one case and venues with editorial notes in the other. This goes beyond the annotations without contradicting them.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is compact, front-loaded with the core purpose, and includes an illustrative example. Each sentence earns its place: one defines scope, and two concisely cover the parameter-dependent behavior. There is no redundancy or filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's moderate complexity, full schema coverage, presence of an output schema, and read-only annotations, the description covers everything needed to invoke it correctly. It explains the required city context, the optional list_id, and what each call returns, making it complete without needing to repeat schema or output details.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the baseline is 3. The description adds extra semantic value by explaining the behavior associated with list_id omission vs. inclusion, which the schema only hints at through the parameter description 'A list id from the no-arg call.' This directly clarifies how the parameters affect the result.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('returns') and names a precise resource: 'Dim Hour's editorial themed lists for a city.' It clearly distinguishes itself from siblings like list_new_venues by emphasizing editorial lists, and it explains the two invocation modes (with and without list_id) so the tool's purpose is unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description clearly states the context: editorial themed lists for a city, and gives concrete usage guidance for when list_id is omitted versus included. It does not explicitly name alternatives or say when not to use this tool, but the editorial focus and conditional behavior make the intended usage clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
fetch and get_venue both describe retrieving the full record for a venue, differing only in an extra long-form story for Iconic 50 venues, making their boundaries unclear. Similarly, search and search_venues both search the same catalog with overlapping descriptions, leaving an agent unsure which to call.
The list_* tools are consistently verb_noun, but search and search_venues repeat the same action with different names, and fetch breaks the otherwise intuitive get_* pattern. The naming is readable but not systematic.
Seven tools is a reasonable count for a venue-discovery server, but redundancy between fetch/get_venue and search/search_venues inflates the set and makes it feel less tight than the domain requires.
The surface covers searching, retrieving details, browsing curated lists, and listing new venues across cities, so core discovery workflows are supported. Minor gaps exist around filtering/sharing list results, but agents can generally complete end-to-end tasks.