Skip to main content
Glama
xuanji86

GunStore-POS Admin MCP

by xuanji86

promote_to_item

Promote an RSR catalog row to a sellable item, transferring manufacturer, model, caliber, prices, and images from the catalog. Requires a payload matching the promotion flow.

Instructions

Promote an RSR catalog row into a sellable Item (manufacturer / model / caliber / prices / images flow in from the catalog). payload mirrors the promote flow, e.g. {rsr_stock_number, item_code?, item_name?, ...}. confirm=true. Find candidates with rsr_catalog_search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
payloadYes
confirmNo
Behavior3/5

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

No annotations provided. Description mentions 'confirm=true' and lists promoted fields but lacks details on permissions, reversibility, or side effects. Adequate but not comprehensive.

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 efficient sentences with no redundancy. Front-loaded purpose and key constraints.

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?

Covers purpose, payload structure, and prerequisite search. Lacks output specification or what happens after promotion. Adequate for the tool's complexity.

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

Parameters4/5

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

Schema coverage 0%, description compensates by exemplifying payload structure (rsr_stock_number, item_code?, item_name?) and explains confirm parameter. Adds meaning beyond empty schema.

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?

Clear verb 'promote' with specific resource transition from 'RSR catalog row' to 'sellable Item'. Distinguishes from siblings like 'rsr_catalog_search' (find candidates) and 'rsr_sync_catalog' (sync catalog).

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?

Explicitly mentions to use 'rsr_catalog_search' to find candidates before this tool. Hints at confirmation requirement with 'confirm=true'. Does not specify when not to use or alternatives.

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/xuanji86/gunstore-pos-mcp'

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