Skip to main content
Glama
Sign In

GunSpec

by io.gunspec
OverviewDiscussionsAdmin

What an attachment fits

gunspec_attachment_firearms
Read-onlyIdempotent

Returns every firearm that one attachment fits, with the supporting evidence for each. Requires the Studio plan.

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": {
      "id": "<id>"
    },
    "name": "gunspec_attachment_firearms"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe attachment slug, e.g. as returned by a list or search tool.
pageNoPage number, from 1.
per_pageNoItems per page, 1 to 100.

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, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds meaningful extra context: the Studio plan requirement and the fact that each result includes supporting evidence, which helps agents anticipate authentication and output shape.

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 short sentences with no filler. The main purpose is stated first, and the access requirement is included as a relevant secondary detail. Every sentence earns its place.

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 straightforward read-only lookup with well-documented pagination parameters, the description covers core behavior, result evidence, and the plan gate. It could mention pagination or output structure, but the schema and annotations are sufficient for an agent 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 parameters are already fully documented. The description adds little about parameter behavior beyond implying the id parameter is the attachment slug, but this does not go beyond what the schema states.

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?

The description explicitly states the action: 'Returns every firearm that one attachment fits, with the supporting evidence for each.' This clearly communicates the relationship direction and distinguishes it from the inverse sibling gunspec_firearm_attachments, which maps a firearm to attachments.

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 usage context is implied by the description: use this when you need to find all firearms compatible with a single attachment. However, it does not explicitly compare against siblings like gunspec_what_fits or gunspec_firearm_attachments, nor does it state when not to use it.

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

All GunSpec toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources