Skip to main content
Glama
DynamicDeals

Gunsnation MCP

by DynamicDeals

get_firearm

Retrieve comprehensive firearm details including specifications, descriptions, and images by providing a specific firearm ID.

Instructions

Get detailed information about a specific firearm by its ID. Returns comprehensive details including specifications, description, and images.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the firearm to retrieve

Implementation Reference

  • The handler function that executes the `get_firearm` tool logic by calling the API client and formatting the response.
    export async function getFirearm(
      client: GunsnationApiClient,
      input: GetFirearmInput
    ): Promise<string> {
      const response = await client.getFirearm({
        id: input.id,
      });
    
      if (!response.success) {
        return `Error: ${response.error.message} (${response.error.code})`;
      }
    
      return formatDetailedFirearm(response.data);
    }
  • Zod schema for validating the input arguments for the `get_firearm` tool.
    export const getFirearmSchema = z.object({
      id: z.union([z.string(), z.number()]).describe('The ID of the firearm to retrieve'),
    });
  • src/server.ts:109-111 (registration)
    Registration and invocation logic within the server's request handler switch statement.
    case 'get_firearm': {
      const input = getFirearmSchema.parse(args);
      const result = await getFirearm(this.apiClient, input);
Behavior3/5

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

With no annotations provided, the description carries the full disclosure burden. It adds valuable context about return values (specifications, description, images) compensating for the lack of output schema. However, it omits other behavioral traits like error handling (what happens if ID is invalid?), authentication requirements, or rate limiting.

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 two-sentence structure is perfectly economical: the first establishes the action and required parameter, while the second describes the return payload. There is no redundant or filler text.

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 simple single-parameter retrieval tool without output schema, the description is adequate. It compensates for the missing output schema by describing return contents. It could be improved by mentioning error states or the relationship to search_firearms, but it covers the essential contract.

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%, so the baseline is 3. The description mentions 'by its ID' which aligns with but does not extend beyond the schema's parameter description. No additional semantic details (e.g., ID format, where to obtain valid IDs) are provided.

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 clearly states the tool retrieves detailed firearm information using a specific ID, with a distinct resource and action. However, it does not explicitly differentiate from sibling 'search_firearms' (e.g., stating this is for exact ID lookups versus search queries), keeping it from a perfect score.

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 phrase 'by its ID' implies usage when an identifier is already known, suggesting when to use it versus the search sibling. However, it lacks explicit guidance such as 'use this when you have a firearm ID; use search_firearms to find IDs by name or criteria.'

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/DynamicDeals/mcp-server-gunsnation'

If you have feedback or need assistance with the MCP directory API, please join our Discord server