Skip to main content
Glama

FFL transfer dealers near a ZIP

find_ffl_dealers
Read-onlyIdempotent

Licensed FFL dealers near a US ZIP code that a gun bought online can ship to: the ones with a known transfer fee first, cheapest fee first, then by distance, with address and phone. Set nfa_only for dealers who handle suppressors and SBRs (SOT).

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": {
      "zip": "<zip>"
    },
    "name": "find_ffl_dealers"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipYes
limitNo
nfa_onlyNoOnly SOT dealers who transfer suppressors and other NFA items
radius_milesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the bar is low; the description still adds real value by disclosing the result ordering (known fee first, cheapest fee, then distance) and returned fields (address, phone). It does not say what happens to dealers with no known fee or whether results are capped by radius/limit.

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 dense sentences with no filler: the resource and use case come first, then ranking/return shape, then the optional filter. Every clause carries information an agent needs.

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

Completeness3/5

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

With no output schema, the description usefully covers ranking and returned fields, but for a geo-search tool it omits how radius_miles and limit shape results and what an empty or fee-unknown result set looks like.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 25%, and the description only elaborates nfa_only (expanding SOT to suppressors and SBRs). The radius_miles search radius and limit semantics are left entirely to bare parameter names, so the description does not compensate for the low coverage.

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 ('Licensed FFL dealers near a US ZIP code') plus the exact use case (a gun bought online shipping there), which clearly separates it from siblings like search_products, get_prices, or gun_laws.

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 online-purchase transfer scenario implies when to use it, and the nfa_only flag hints at a specialized sub-case, but there is no explicit when-to-use/when-not guidance or named alternative for related needs.

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