Skip to main content
Glama
wspotter

MCP Art Supply Store

by wspotter

check_inventory

Check current stock levels, reorder status, and supplier details for specific art supply products or categories to manage inventory effectively.

Instructions

Check current inventory levels for a specific product or category. Returns stock quantity, reorder status, and supplier information.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
searchYesProduct name, SKU, or category to search for

Implementation Reference

  • The handler function for the 'check_inventory' tool. It filters the mock inventory data based on the search parameter (product name, SKU, or category) and returns detailed stock information including low stock warnings.
    case 'check_inventory': {
      const search = String(args?.search || '').toLowerCase();
      const results = storeData.inventory.filter(item =>
        item.name.toLowerCase().includes(search) ||
        item.id.toLowerCase().includes(search) ||
        item.category.toLowerCase().includes(search)
      );
      return {
        content: [{
          type: 'text',
          text: results.length > 0
            ? `Found ${results.length} item(s):\n\n${results.map(item => 
                `${item.name} (${item.id})\n- Category: ${item.category}\n- Stock: ${item.quantity} units${item.quantity <= item.reorderLevel ? ' ⚠️ LOW STOCK' : ''}\n- Price: $${item.price}\n- Supplier: ${item.supplier}\n- Last Restocked: ${item.lastRestocked}`
              ).join('\n\n')}`
            : `No items found matching "${args?.search}"`
        }]
      };
    }
  • The input schema definition for the 'check_inventory' tool, specifying a required 'search' string parameter.
    {
      name: 'check_inventory',
      description: 'Check current inventory levels for a specific product or category. Returns stock quantity, reorder status, and supplier information.',
      inputSchema: {
        type: 'object',
        properties: {
          search: { type: 'string', description: 'Product name, SKU, or category to search for' },
        },
        required: ['search'],
      },
    },
  • src/index.ts:516-518 (registration)
    Registration of all tools including 'check_inventory' via the ListToolsRequestSchema handler that returns the tools array containing the tool definition.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return { tools };
    });
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the return values ('stock quantity, reorder status, and supplier information'), which is helpful, but lacks details on permissions, rate limits, error handling, or whether this is a read-only operation. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 description is efficiently structured in two sentences: the first states the purpose, and the second specifies the return values. Every sentence adds value with no wasted words, making it front-loaded and easy to parse for an AI agent.

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

Completeness3/5

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

Given the tool's moderate complexity (1 parameter, no output schema, no annotations), the description is partially complete. It covers the purpose and return values, but lacks behavioral details like permissions or error handling. Without annotations or an output schema, more context on how the tool behaves would improve completeness for safe invocation.

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?

The input schema has 100% description coverage, with the parameter 'search' documented as 'Product name, SKU, or category to search for.' The description adds minimal value beyond this, only implying the parameter's purpose without providing additional syntax or format details. With high schema coverage, the baseline score of 3 is appropriate.

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's purpose: 'Check current inventory levels for a specific product or category.' It specifies the verb ('Check') and resource ('inventory levels'), and distinguishes it from siblings like 'get_inventory_value' or 'get_low_stock_items' by focusing on specific product/category lookup. However, it doesn't explicitly differentiate from 'search_products' or 'update_stock', which slightly limits sibling distinction.

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 description implies usage context by specifying 'for a specific product or category,' suggesting when to use this tool. However, it provides no explicit guidance on when to use alternatives like 'get_low_stock_items' for alerts or 'search_products' for broader searches, and lacks prerequisites or exclusions. This leaves usage somewhat open to interpretation.

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/wspotter/mcpart'

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