Skip to main content
Glama

Check a trip with a gun

check_gun_travel
Read-onlyIdempotent

Check a drive or flight between two US states with a firearm: every state on the route, what each one says about what you are bringing (clear, caution or stop), what to do before you cross, and safer routes when one exists. The same check as the GunPartPicker gun travel checker. Items: pistol (Carry pistol (EDC)), longgun (AR-15 or other semi-auto rifle), mags (Magazines over 10 rounds), suppressor (Suppressor), sbr (SBR), brace (Braced AR pistol), frt (Forced reset trigger), binary (Binary trigger), hollowpoint (Hollow point ammo).

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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "check_gun_travel"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesState the trip ends in
fromYesState the trip starts in: name or two letter code
modeNoauto drives when there is a land routeauto
routeNoThe states the highway crosses, in order, as two letter codes, when the road is known
bringingNoWhat is coming along
magazine_sizeNoLargest magazine coming along, in rounds

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: it discloses the shape of the answer (each state on the route rated clear/caution/stop), that it suggests pre-crossing actions, and that it can return safer routes. It does not mention disclaimers or coverage limits (territories, local ordinances), which keeps it from a 5.

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?

The first sentence is front-loaded with the core purpose and the return contents, and it is dense but readable. The trailing items list largely restates the schema enum, though the parenthetical glosses justify most of that space.

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 six parameters, full schema coverage and no output schema, the description carries the burden of explaining what comes back, and it does so: route states, per-state verdicts, actions before crossing, and alternative routes. Remaining gaps are modest — no statement of jurisdictional scope limits or of how verdicts should be interpreted legally.

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 the baseline is 3. The description does gloss the cryptic enum values (frt as 'Forced reset trigger', sbr as 'SBR', brace as 'Braced AR pistol'), which is genuine added meaning, but it says nothing about the from/to, mode, route or magazine_size parameters beyond what the schema already documents.

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 opens with a specific verb and resource: 'Check a drive or flight between two US states with a firearm', and it enumerates the outputs (per-state verdicts, pre-crossing actions, safer routes). That makes the tool's job unmistakable. It does not explicitly distinguish itself from the similarly-scoped sibling 'gun_laws', so it stops short of a 5.

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?

Usage is implied by the phrasing 'Check a drive or flight between two US states with a firearm', and the mode/route parameters reinforce the trip-checking scenario. However, there is no explicit when-to-use versus when-not guidance and no sibling is named as an alternative (e.g. for a single-state lookup versus a multi-state route).

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