Cork & Curve wine travel

search_places

Read-onlyIdempotent

Search verified venues (read-only). Filter by text, city, kind (a topic such as vineyards, tasting-rooms, wine-bars, wine-restaurants, wine-retailers, distilleries, or a group: visit, drink, buy, do), cuisine, dietary, price tier, opening time, or near a coordinate. Results are ranked by relevance then editorial score and carry provenance (source URL, checked_on, open_status), hours, a page URL to cite and a tracked booking link where one exists. Returns at most limit items; an unknown city returns {did_you_mean: [...]} instead of a list.

Input Schema

TableJSON Schema

Name	Required	Description
`city`	No	City slug or name, e.g. 'burgenland' or 'New York City'. Unknown cities answer with did_you_mean.
`kind`	No	A topic slug (vineyards, tasting-rooms, wine-bars, wine-restaurants, wine-retailers, distilleries...) or a group: visit, drink, buy, do.
`near`	No	'lat,lng' to search around a point; results then sort by distance.
`limit`	No	Maximum results (1-100).
`query`	No	Free text: a venue name, dish, cuisine, neighbourhood or theme.
`offset`	No	Skip this many results, for paging.
`country`	No	Country slug or name, e.g. 'italy'. Optional where city is given.
`cuisine`	No	Cuisine slug or name, e.g. 'sichuan', 'neapolitan pizza'.
`dietary`	No	vegan, vegetarian, gluten-free, halal, kosher...
`open_at`	No	'now', a weekday and time such as 'sunday 10:00', or an ISO datetime (UTC). Venues with unparseable hours are returned last, flagged.
`radius_km`	No	Radius for near, in km.
`price_tier`	No	The site's tier symbols for the country, e.g. '€€' or '$$$'.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedSep 18, 2026

addedInput schema / properties / city / description

Added value: +"City slug or name, e.g. 'burgenland' or 'New York City'. Unknown cities answer with did_you_mean."

addedInput schema / properties / country / description

Added value: +"Country slug or name, e.g. 'italy'. Optional where city is given."

addedInput schema / properties / cuisine / description

Added value: +"Cuisine slug or name, e.g. 'sichuan', 'neapolitan pizza'."

addedInput schema / properties / dietary / description

Added value: +"vegan, vegetarian, gluten-free, halal, kosher..."

addedInput schema / properties / kind / description

Added value: +"A topic slug (vineyards, tasting-rooms, wine-bars, wine-restaurants, wine-retailers, distilleries...) or a group: visit, drink, buy, do."

addedInput schema / properties / limit / description
```
Added value: +"Maximum results (1-100)."
```

addedInput schema / properties / near / description

Added value: +"'lat,lng' to search around a point; results then sort by distance."

addedInput schema / properties / offset / description

Added value: +"Skip this many results, for paging."

addedInput schema / properties / open_at / description

Added value: +"'now', a weekday and time such as 'sunday 10:00', or an ISO datetime (UTC). Venues with unparseable hours are returned last, flagged."

addedInput schema / properties / price_tier / description

Added value: +"The site's tier symbols for the country, e.g. '€€' or '$$$'."

addedInput schema / properties / query / description

Added value: +"Free text: a venue name, dish, cuisine, neighbourhood or theme."

addedInput schema / properties / radius_km / description
```
Added value: +"Radius for near, in km."
```

Changed3 schema fields changedSep 18, 2026

addedInput schema / properties / dietary

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Dietary"
+}

addedInput schema / properties / open_at

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Open At"
+}

addedInput schema / properties / price_tier

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Price Tier"
+}

First observedSep 18, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering safety. The description adds valuable behavioral detail beyond annotations: relevance then editorial score ranking, provenance fields (source URL, checked_on, open_status), hours, citation URL, tracked booking link, a hard limit on results, and the did_you_mean response for unknown cities. This significantly aids the agent in predicting output and edge cases.

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 a single, well-structured paragraph that front-loads the core purpose and then efficiently lists filters and behavioral details. Every sentence adds value, with no fluff or repetition. It is appropriately sized for a 12-parameter search tool.

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?

Given the complexity (12 optional parameters, output schema present), the description covers the purpose, all filter categories, ranking behavior, provenance, limit semantics, and the unknown-city edge case. The output schema handles return-value details, so nothing critical is missing. The description is complete for correct invocation.

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% and every parameter has a detailed schema description (e.g., city slug, near 'lat,lng', open_at format). The description merely summarizes these filters without adding syntax or additional meaning beyond what the schema already provides. Per rubric, baseline of 3 applies; the description adds minimal extra semantic value.

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 opens with a specific verb and resource: 'Search verified venues (read-only).' It clearly distinguishes this tool from siblings like car_hire, stays, and experiences by listing venue-specific filters (kind, cuisine, price tier). An agent can immediately understand what this tool is for without ambiguity.

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?

The description clearly states what it does and enumerates filter options, giving strong contextual guidance. It does not explicitly contrast with sibling tools such as 'place' (likely single-venue lookup) or advise when not to use it, but the purpose is distinct enough that an agent can infer appropriate use. Minor gap: no explicit exclusions or alternatives mentioned.

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

All Cork & Curve wine travel 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?