Skip to main content
Glama

get_available_sources

Retrieve available deal sources and providers to enable comparison shopping across multiple platforms.

Instructions

Get list of available deal sources/providers

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The primary handler function for the 'get_available_sources' MCP tool. It fetches available providers from the aggregator and returns a standardized JSON response.
    private async handleGetAvailableSources() {
      const sources = this.aggregator.getProviders();
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify({
              success: true,
              sources: sources
            }, null, 2),
          },
        ],
      };
    }
  • src/server.ts:275-282 (registration)
    Tool registration in the listTools response, defining name, description, and input schema (empty object since no parameters required).
    {
      name: 'get_available_sources',
      description: 'Get list of available deal sources/providers',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • Input schema definition for the tool (empty properties as it takes no arguments).
    inputSchema: {
      type: 'object',
      properties: {},
    },
  • Supporting helper method that returns the names of all registered deal providers, called by the tool handler.
    getProviders(): string[] {
      return Array.from(this.providers.keys());
    }
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 states the tool retrieves a list, implying a read-only operation, but doesn't specify if it requires authentication, has rate limits, returns structured data, or handles errors. This leaves significant gaps in understanding its 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 directly states the tool's purpose without any wasted words. It's front-loaded and appropriately sized for a simple tool, making it easy to parse quickly.

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 simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate. It explains what the tool does but lacks details on behavior, usage context, or output format, which could be helpful for an AI agent despite the low 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?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, but since there are no parameters, this is appropriate. A baseline of 4 is applied as it adequately addresses the lack of parameters without redundancy.

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 list') and resource ('available deal sources/providers'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its siblings (like 'search_deals' or 'filter_deals'), which also deal with deal-related data, so it doesn't reach the highest score.

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. With sibling tools like 'search_deals' and 'filter_deals' available, there's no indication of whether this tool is for metadata retrieval, initial setup, or other contexts, leaving usage ambiguous.

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/karthiksivaramms/bargainer-mcp-client'

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