Skip to main content
Glama
xuanji86

FastBound MCP

by xuanji86
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get item

get_item
Read-only

Retrieve a single firearm record by its FastBound GUID or external ID, providing read-only access to the item's details.

Instructions

Retrieve a single firearm record by FastBound GUID id or by your externalId. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe id value to look up.
idTypeNoWhether `id` is the FastBound GUID (default) or your externalId.
accountNoWhich configured FastBound account to use for this one call — an alias or account number (see list_accounts). Omit to use the active account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.0
    • addedInput schema / properties / account
      Added value: +{
+  "description": "Which configured FastBound account to use for this one call — an alias or account number (see list_accounts). Omit to use the active account.",
+  "type": "string"
+}
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

The annotations already provide readOnlyHint=true, and the description reinforces this with 'Read-only.' It adds useful context about the single-record scope and identifier types, though it doesn't describe not-found behavior or any external-world caveat hinted by openWorldHint=true.

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?

One tight sentence names the action, the object, the key fields, and the read-only nature. Every word earns its place and the most important scoping information is front-loaded.

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 single-record lookup with one required parameter and clear annotations, the description is largely sufficient. It doesn't explain the return shape or error handling, but the output schema is absent and the stated purpose is enough for a competent agent to invoke 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 the baseline applies. The description adds a little meaning by explicitly mentioning FastBound GUID and externalId, which maps to the id/idType relationship, but it doesn't significantly extend what the schema already documents.

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 uses a specific verb ('Retrieve'), names the resource ('a single firearm record'), and identifies the two lookup keys (FastBound GUID or externalId). This clearly distinguishes it from search/listing siblings like search_items and from acquisition/disposition record tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description makes the direct-lookup use case clear: retrieve one specific item by a known identifier. It doesn't explicitly call out search_items as the alternative for queries/filters, but the context strongly implies that this is the point lookup tool.

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

Deploy Server

Other Tools