Skip to main content
Glama
wspotter

MCP Art Supply Store

by wspotter

get_supplier_info

Retrieve supplier contact details, lead times, and minimum order requirements to manage art supply procurement and maintain business operations.

Instructions

Get detailed supplier information including contact details, lead times, and minimum order requirements.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
supplierNameYesSupplier name or ID

Implementation Reference

  • Executes the get_supplier_info tool: searches mock supplier data by name/ID, returns contact details, lead times, min order, and top products from that supplier.
      const supplierName = String(args?.supplierName || '').toLowerCase();
      const supplier = storeData.suppliers.find(s =>
        s.name.toLowerCase().includes(supplierName) ||
        s.id.toLowerCase() === supplierName
      );
      
      if (!supplier) {
        return { content: [{ type: 'text', text: `āŒ Supplier not found: "${args?.supplierName}"` }] };
      }
      
      const supplierProducts = storeData.inventory.filter(i => i.supplier === supplier.name);
      
      return {
        content: [{
          type: 'text',
          text: `šŸ¢ ${supplier.name} (${supplier.id})\n\nšŸ“§ ${supplier.contact}\nšŸ“± ${supplier.phone}\nā±ļø Lead Time: ${supplier.leadTime}\nšŸ’µ Minimum Order: $${supplier.minOrder}\n\nšŸ“¦ Products from this supplier: ${supplierProducts.length}\n${supplierProducts.slice(0, 5).map(p => `• ${p.name}`).join('\n')}`
        }]
      };
    }
  • Defines the tool schema: name, description, and inputSchema requiring supplierName parameter.
      name: 'get_supplier_info',
      description: 'Get detailed supplier information including contact details, lead times, and minimum order requirements.',
      inputSchema: {
        type: 'object',
        properties: {
          supplierName: { type: 'string', description: 'Supplier name or ID' },
        },
        required: ['supplierName'],
      },
    },
  • src/index.ts:516-518 (registration)
    Registers the tool list (including get_supplier_info) for MCP ListTools requests.
    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 implies a read-only operation ('Get'), but does not specify if it requires authentication, has rate limits, returns paginated results, or what happens on errors. For a tool with no annotation coverage, this is a significant gap in transparency about its behavior and constraints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads the main purpose and includes relevant details without unnecessary words. It avoids redundancy and is appropriately sized for the tool's complexity, though it could be slightly more structured by separating usage guidelines.

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?

Given the lack of annotations and output schema, the description is incomplete. It does not explain the return format, error handling, or behavioral traits like data freshness or access permissions. For a tool that retrieves detailed information, more context is needed to guide the agent effectively, making it inadequate for full understanding.

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 'supplierName' documented as 'Supplier name or ID'. The description does not add any additional meaning beyond this, such as format examples or validation rules. With high schema coverage, the baseline score of 3 is appropriate as the schema handles the parameter documentation adequately.

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 action ('Get detailed supplier information') and specifies the resource ('supplier'), along with examples of what information is included ('contact details, lead times, and minimum order requirements'). However, it does not explicitly differentiate this tool from sibling tools like 'compare_supplier_prices' or 'lookup_customer', which might also involve supplier data, so it lacks sibling differentiation.

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. For example, it does not mention when to prefer this over 'compare_supplier_prices' or if it's for retrieving basic vs. detailed supplier info. There is no context on prerequisites, exclusions, or typical use cases, leaving the agent with no usage direction.

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