Skip to main content
Glama

add_shop_item

Add a new shop item with defined price, stock, effects (coin rewards, exp bonuses, special actions), and purchase limits.

Instructions

Create a new shop item with price, stock, effects, and purchase limits. Items can have custom usage effects like coin rewards, exp bonuses, or special actions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesItem name (required)
descNoItem description
iconNoIcon URL
title_color_stringNoTitle color in hex format (e.g., "#66CCFF")
priceNoPurchase price in coins (default: 0)
stock_numberNoInitial stock quantity (-1 for unlimited, default: -1)
action_textNoCustom text for use button
disable_purchaseNoDisable purchasing (default: false)
disable_useNoDisable using (default: false)
categoryNoCategory ID (0 for default)
effectsNoItem usage effects. Example: [{"type":2,"info":{"min":100,"max":200}}] for coin reward
purchase_limitNoPurchase frequency limits. Example: [{"type":"daily","value":5}]
Behavior2/5

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

No annotations provided, and the description does not disclose behavioral traits such as being destructive, requiring authentication, or having rate limits. For a creation tool, the description lacks important safety and side-effect information.

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 sentences with no redundancy. Every sentence adds value: the first states the action and key attributes, the second provides a concrete example of custom effects.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 12 parameters and no output schema, the description lacks details on return values, success indicators, required permissions, or side effects. It is not complete enough for an agent to use effectively without additional context.

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% with all parameters documented. The description adds examples of custom effects (coin rewards, exp bonuses), which adds value beyond the schema, but does not significantly enhance understanding of complex parameters like effects or purchase_limit.

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?

Description clearly states 'Create a new shop item' with specific attributes (price, stock, effects, purchase limits) and examples of custom effects, distinguishing it from sibling tools like edit_shop_item or list_shop_items.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives, no prerequisites, and no context for when not to use it. Users must infer from the tool name and sibling names.

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/derekprovance/lifeup-mcp'

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