Skip to main content
Glama

lookup_liquor_license

Look up liquor licenses in Texas, California, New York, Virginia, Florida, Oregon, Colorado or the City of Chicago (state IL) by business name, owner (legal) name, premises address or license number. Returns license number, type, status and expiration date from the state's own records (TABC, California ABC, New York SLA, Virginia ABC, Florida DBPR). 1 credit per returned license.

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>",
      "query": "<query>"
    },
    "name": "lookup_liquor_license"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax licenses to return (<=25). Each costs 1 credit.
queryYesBusiness name, owner name, address or license number (3+ characters).
stateYesTwo-letter state. IL covers City of Chicago licences only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / state / description
      Previous value: -"Two-letter state."New value: +"Two-letter state. IL covers City of Chicago licences only."
    • changedInput schema / properties / state / enum
      Previous value: -[
      -  "TX",
      -  "CA",
      -  "NY",
      -  "VA",
      -  "FL"
      -]New value: +[
      +  "TX",
      +  "CA",
      +  "NY",
      +  "VA",
      +  "FL",
      +  "OR",
      +  "CO",
      +  "IL"
      +]
  2. Added

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and discloses important behavior: the authoritative state sources, returned fields, IL/Chicago limitation, and credit cost per returned license. It does not mention pagination, exact-match vs partial-match behavior, or any auth/rate-limit constraints, which leaves some operational details unspecified.

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 no wasted wording. It front-loads the core capability and coverage, then follows with return fields, data sources, and cost.

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 three-parameter lookup tool with full schema coverage and no output schema, the description is nearly complete: it covers coverage, search fields, return fields, sources, and cost. Minor gaps remain around pagination and match behavior, but an agent has enough information 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 description coverage is 100%, so all three parameters are already documented in the schema. The description reinforces the query fields and notes that IL covers Chicago only, but adds no meaningful syntax or format detail beyond 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?

The description states a specific verb and resource: look up liquor licenses, with named geographic coverage and searchable fields. It is clear what the tool does, but it does not explicitly distinguish itself from the sibling tools such as coverage or venue_signals.

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?

Use is implied by the description of searchable fields and coverage, but there is no explicit when-to-use or when-not-to-use guidance, and no named alternative tool. The agent can infer the tool's role but receives no routing instructions.

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