Skip to main content
Glama
wspotter

MCP Art Supply Store

by wspotter

auto_respond_common_questions

Automatically answer customer questions about store hours, location, stock availability, and pricing to reduce response time and improve customer service efficiency.

Instructions

Enable automatic responses to frequently asked questions (hours, location, stock availability).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
enableYesEnable or disable auto-responses
questionTypesNoTypes to auto-respond: hours, location, stock, pricing (comma-separated)

Implementation Reference

  • src/index.ts:487-497 (registration)
    Registers the 'auto_respond_common_questions' tool, including its name, description, and input schema for enabling/disabling auto-responses to common FAQs.
    {
      name: 'auto_respond_common_questions',
      description: 'Enable automatic responses to frequently asked questions (hours, location, stock availability).',
      inputSchema: {
        type: 'object',
        properties: {
          enable: { type: 'boolean', description: 'Enable or disable auto-responses' },
          questionTypes: { type: 'string', description: 'Types to auto-respond: hours, location, stock, pricing (comma-separated)' },
        },
        required: ['enable'],
      },
  • The handler function for 'auto_respond_common_questions' tool. Simulates toggling auto-responses for specified question types and returns a status message. Mock implementation noting production would use Messenger API.
    case 'auto_respond_common_questions': {
      const enable = Boolean(args?.enable ?? false);
      const questionTypes = String(args?.questionTypes || 'hours,location,stock');
      
      const types = questionTypes.split(',').map(t => t.trim());
    
      return {
        content: [{
          type: 'text',
          text: `šŸ¤– Auto-Response Settings ${enable ? 'ENABLED' : 'DISABLED'}\n\n${enable ? 'āœ… Will auto-respond to:\n' + types.map(type =>
            `  • ${type.charAt(0).toUpperCase() + type.slice(1)} questions`
          ).join('\n') : 'āŒ Auto-responses are disabled'}\n\nāš™ļø Note: Auto-responses help provide quick answers, but always review and personalize when possible!\n\nšŸ’” This is a mock feature. In production, this would integrate with Facebook's Messenger API for automated responses.`
        }]
      };
    }
  • src/dashboard.ts:83-83 (registration)
    Mock registration of the tool in the dashboard's toolsData for UI display and simulation.
    { name: 'auto_respond_common_questions', description: 'Auto-respond to FAQs', category: 'Social Media Management' },
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions enabling/disabling auto-responses but doesn't describe what happens when enabled (e.g., whether responses are immediate, what format they take, if they're customizable, or any rate limits). This leaves significant gaps for a configuration tool that likely modifies system behavior.

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 a single, efficient sentence that gets straight to the point with zero wasted words. It's appropriately sized for a simple configuration tool and front-loads the core functionality.

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 configuration tool with no annotations and no output schema, the description is insufficient. It doesn't explain what 'automatic responses' entail, how they're delivered, what the response content looks like, or any side effects. The agent would need to guess about the tool's behavior and outcomes.

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 schema already documents both parameters thoroughly. The description adds minimal value beyond the schema - it mentions 'hours, location, stock availability' which partially overlaps with the 'questionTypes' parameter examples, but doesn't provide additional semantic context. Baseline 3 is appropriate when schema does the heavy lifting.

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: 'Enable automatic responses to frequently asked questions' with specific examples (hours, location, stock availability). This provides a clear verb+resource combination, though it doesn't explicitly differentiate from sibling tools like 'suggest_comment_reply' or 'check_inventory' which might handle similar domains differently.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, appropriate contexts, or exclusions. For example, it doesn't clarify if this should be used instead of manual responses or other automation tools in the sibling list.

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