ureweries

Breweries By City

breweries_by_city

Read-onlyIdempotent

Find all breweries in a city (e.g., "Portland", "Denver"). Returns location, type, and contact details for each.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`city`	Yes	City name to search breweries in (e.g., "Portland", "Denver")
`limit`	No	Maximum number of results to return (default 10, max 50)

Output Schema

TableJSON Schema

Name	Required	Description
`city`	Yes	City name searched
`count`	Yes	Number of breweries returned
`breweries`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "breweries": {
+      "items": {
+        "properties": {
+          "address": {
+            "description": "Full street address",
+            "type": "string"
+          },
+          "city": {
+            "description": "City name",
+            "type": "string"
+          },
+          "coordinates": {
+            "description": "Geographic coordinates if available",
+            "oneOf": [
+              {
+                "properties": {
+                  "latitude": {
+                    "description": "Latitude coordinate",
+                    "type": "number"
+                  },
+                  "longitude": {
+                    "description": "Longitude coordinate",
+                    "type": "number"
+                  }
+                },
+                "required": [
+                  "latitude",
+                  "longitude"
+                ],
+                "type": "object"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "country": {
+            "description": "Country name",
+            "type": "string"
+          },
+          "id": {
+            "description": "Brewery ID",
+            "type": "string"
+          },
+          "name": {
+            "description": "Brewery name",
+            "type": "string"
+          },
+          "phone": {
+            "description": "Phone number",
+            "type": "string"
+          },
+          "postal_code": {
+            "description": "Postal/zip code",
+            "type": "string"
+          },
+          "state": {
+            "description": "State or province",
+            "type": "string"
+          },
+          "type": {
+            "description": "Brewery type (e.g., micro, macro, pub)",
+            "type": "string"
+          },
+          "website": {
+            "description": "Website URL",
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "name",
+          "type",
+          "address",
+          "city",
+          "state",
+          "postal_code",
+          "country",
+          "coordinates",
+          "phone",
+          "website"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "city": {
+      "description": "City name searched",
+      "type": "string"
+    },
+    "count": {
+      "description": "Number of breweries returned",
+      "type": "number"
+    }
+  },
+  "required": [
+    "city",
+    "count",
+    "breweries"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "city": "Portland"
+  },
+  {
+    "city": "Denver",
+    "limit": 15
+  }
+]

First observedApr 14, 2026

TDQS

A3.8/5.0

Behavior3/5

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

The annotations already indicate a safe read operation, so the bar is lower. The description adds the return fields (location, type, contact details), but does not discuss pagination, ordering, or data freshness. This is some added context beyond annotations.

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 two sentences with clear, front-loaded information. No redundant text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read tool with full schema coverage and an output schema, the description adequately explains functionality and return fields. Minor omissions like default limit behavior are already in the schema.

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?

The input schema covers 100% of parameters with descriptions for city and limit. The description adds no additional parameter semantics, repeating the city examples but not elaborating on limit behavior.

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 clearly states 'Find all breweries in a city' with concrete examples, specifying the action and resource. It distinguishes from sibling tools like get_brewery by focusing on city-level listing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when you need breweries by city, but does not explicitly explain when to use this over alternatives like search_breweries or get_brewery. No exclusions or comparisons are provided.

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

All ureweries 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.