Skip to main content
Glama
comparedge

mcp-server-comparedge

Official

get_pricing

Retrieve verified pricing breakdowns for any tool, including all plans, prices, and token pricing.

Instructions

Retrieve complete verified pricing breakdown for a specific tool, including all plans, prices, highlights, and token pricing where applicable.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesTool slug identifier

Implementation Reference

  • The getPricing function that executes the tool logic. It fetches pricing data for a given tool slug, returns free plan info, plans with prices and highlights, token pricing (if applicable), and a ComparEdge URL.
    async function getPricing(args) {
      const { slug } = args;
      const allPricing = await getAllPricing();
    
      const entry = allPricing.find(t => t.slug === slug);
      if (!entry) return `Pricing data not found for "${slug}".`;
    
      const lines = [
        `Pricing: ${entry.name || slug}`,
        `Free plan: ${entry.freePlan ? 'Yes' : 'No'}`,
        `Verified at: ${entry.verifiedAt || 'N/A'}`,
      ];
    
      if (entry.plans && entry.plans.length > 0) {
        lines.push('\nPlans:');
        entry.plans.forEach(p => {
          const price = p.price !== undefined ? formatPrice(p.price) : 'N/A';
          lines.push(`  ${p.name}: ${price}`);
          if (p.highlights && p.highlights.length > 0) {
            const h = Array.isArray(p.highlights) ? p.highlights : [p.highlights];
            h.forEach(hl => lines.push(`    - ${hl}`));
          }
        });
      }
    
      if (entry.tokenPricing) {
        lines.push('\nToken pricing:');
        if (typeof entry.tokenPricing === 'object') {
          Object.entries(entry.tokenPricing).forEach(([k, v]) => lines.push(`  ${k}: ${v}`));
        } else {
          lines.push(`  ${entry.tokenPricing}`);
        }
      }
    
      lines.push(`\nComparEdge URL: ${pricingURL(slug)}`);
      return lines.join('\n');
    }
  • Input schema definition for the 'get_pricing' tool, specifying it accepts a required 'slug' string parameter.
    {
      name: 'get_pricing',
      description: 'Retrieve complete verified pricing breakdown for a specific tool, including all plans, prices, highlights, and token pricing where applicable.',
      inputSchema: {
        type: 'object',
        properties: {
          slug: { type: 'string', description: 'Tool slug identifier' },
        },
        required: ['slug'],
      },
    },
  • index.js:455-455 (registration)
    Dispatch routing: case 'get_pricing' maps to the getPricing(args) function in the callTool switch statement.
    case 'get_pricing':     return getPricing(args);
  • Helper function pricingURL(slug) used by the getPricing handler to generate the full ComparEdge pricing URL.
    function pricingURL(slug) {
      return `${SITE_BASE}/pricing/${slug}-pricing`;
    }
  • Helper function formatPrice(price) used by getPricing to format pricing values as '$X/mo' or 'Free'.
    function formatPrice(price) {
      if (price === null || price === undefined) return 'N/A';
      if (price === 0) return 'Free';
      return `$${price}/mo`;
    }
Behavior3/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. It discloses that the operation is a retrieval (read) and claims completeness and verification, but lacks details on authentication, rate limits, or error behavior for invalid slugs.

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, well-structured sentence that front-loads the main action and includes key details. Every word contributes meaning with no redundancy.

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

Completeness4/5

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

Given the simple input (1 required parameter) and no output schema, the description adequately explains what is returned (pricing plans, highlights, token pricing). It could be improved by mentioning response format or error handling, but it is largely complete for a straightforward retrieval tool.

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% for the single parameter 'slug'. The description adds minimal value beyond the schema's 'Tool slug identifier', reinforcing that slug identifies the specific tool. No additional constraints or formats are provided.

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?

The description clearly states the action ('Retrieve'), the resource ('complete verified pricing breakdown for a specific tool'), and lists included elements. It distinguishes itself from siblings like 'get_tool' (general info) and 'get_alternatives' (alternatives).

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 for retrieving pricing, but provides no explicit guidance on when to use this tool versus alternatives like 'compare_tools' or 'get_tool'. No when-not-to-use or exclusion criteria mentioned.

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/comparedge/mcp-server-comparedge'

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