Skip to main content
Glama

Find a license by name

find_license
Read-only

Look up one business by name in a state's liquor license filings: its license type, status, place and date. Sorted by name; address and contacts are on the paid feed.

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

Input Schema

NameRequiredDescriptionDefault
nameYesBusiness or trade name, at least three letters
stateYesTwo-letter state code, e.g. TX

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the description needn't re-establish safety. It adds real context beyond that: results are sorted by name, and address/contact fields are deliberately excluded from this feed, which tells the agent not to expect them. It doesn't address what happens when a name matches multiple businesses, though the sorting hint implies a list.

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?

Two tight sentences, front-loaded with the core action and return fields, followed by the scoping/coverage caveat. No filler or restatement of the title.

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?

With only two fully documented parameters and no output schema, the description usefully names the returned fields and notes the paid-feed boundary. The remaining gap is multi-match behavior — whether one exact result or a name-sorted set is returned — which matters for how the agent interprets output.

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%, with both parameters documented including the 'at least three letters' constraint and the two-letter state format. The description adds no syntax or matching rules (exact vs partial name, case sensitivity) beyond what the schema already states, so baseline 3 applies.

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?

States a specific verb and resource: look up one business by name within a state's liquor license filings. It also enumerates the returned fields (license type, status, place, date), which no sibling tool (county_activity, license_timing, list_states, plans, sample_filings) offers, so an agent can distinguish it immediately.

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 single-business, by-name lookup framing implies when to use it, but there is no explicit when-to-use or when-not guidance and no sibling is named as an alternative for adjacent needs (e.g., aggregate/timing queries). Usage must be inferred from the description.

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