Skip to main content
Glama

new_openings

Find restaurants/bars about to open in a state, ranked by opening_score (0-100). Fuses liquor licenses, food permits and new-business filings into one scored venue. signal_types on each lead are 'liquor', 'food_permit' and 'business'. Live states: NY, TX, IL, OR, CO, WA, CA (call coverage for the current list). 1 credit per returned lead. Each lead has a contact block: subscribers get the owner name from the filing plus phone (many NYC venues) and owner mailing address (most TX venues) where public records carry them; trial keys see contact.locked with contact.available telling whether details exist.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "state": "<state>"
    },
    "name": "new_openings"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax leads to return (<=100). Each lead costs 1 credit.
stateYesTwo-letter state, e.g. NY, TX, IL, OR, CO, WA, CA. Use `coverage` to see live states.
min_scoreNoMinimum opening_score (0-100). Fused multi-signal venues rank highest; 30 includes recent issued-liquor leads, 80+ is a hot multi-signal lead.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / limit / default
      Previous value: -25New value: +10
    • changedInput schema / properties / limit / description
      Previous value: -"Max leads to return (<=100)."New value: +"Max leads to return (<=100). Each lead costs 1 credit."
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses per-lead credit cost, the live-state restriction, the signal source types, and crucially the tier-dependent `contact` behavior (subscribers get owner name/phone/address where public records carry them; trial keys see `contact.locked`). An agent knows cost, availability limits, and data-access constraints before calling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and ranking are front-loaded, followed by coverage, cost, and the contact/tier caveat in a compact sequence. The final sentence about `contact` is long but every clause is decision-relevant; no filler.

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?

There is no output schema, yet the description explains the return shape an agent needs: scored venues with `opening_score`, `signal_types` values, and a `contact` block with its tier semantics. Combined with cost and coverage notes, an agent has enough to call and interpret results.

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%, and the schema already documents `limit` cost, `state` format, and the `min_score` tiers (30 vs 80+), so the description adds little parameter-level meaning. The baseline of 3 applies when the schema does the heavy lifting.

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 ('Find restaurants/bars about to open in a state'), plus the ranking criterion ('ranked by opening_score 0-100') and what data is fused. That is enough for an agent to distinguish it from a generic search or from the `coverage` sibling.

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 gives clear context for use (prospecting venues about to open) and routes the agent to `coverage` for the live-state list before guessing a state. It does not explicitly say when to prefer `venue_signals` or `watch_area` instead, so there are no stated exclusions.

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