Skip to main content
Glama
123Ergo

unphurl-mcp

get_pricing

Retrieve available URL analysis credit packages and their pricing. Compare one-time purchase options with credit counts and per-credit costs.

Instructions

Show available pipeline check credit packages and pricing. Returns all packages with credit counts and prices.

Packages (one-time purchase, no subscription):

  • Starter: 100 credits for $9 ($0.09 each)

  • Standard: 500 credits for $39 ($0.078 each)

  • Pro: 2,000 credits for $99 ($0.0495 each)

  • Scale: 10,000 credits for $399 ($0.0399 each)

Most URL lookups are free (known domains and cached domains). Credits are only consumed when an unknown domain runs through the full analysis pipeline. In typical use, 95-99% of URLs resolve free.

This tool does not require an API key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'get_pricing' tool. Registered via server.registerTool('get_pricing', ...), it calls api.pricing() and returns the result. No auth required.
      // --- get_pricing ---
      // No auth required
      server.registerTool(
        "get_pricing",
        {
          description: `Show available pipeline check credit packages and pricing. Returns all packages with credit counts and prices.
    
    Packages (one-time purchase, no subscription):
    - Starter: 100 credits for $9 ($0.09 each)
    - Standard: 500 credits for $39 ($0.078 each)
    - Pro: 2,000 credits for $99 ($0.0495 each)
    - Scale: 10,000 credits for $399 ($0.0399 each)
    
    Most URL lookups are free (known domains and cached domains). Credits are only consumed when an unknown domain runs through the full analysis pipeline. In typical use, 95-99% of URLs resolve free.
    
    This tool does not require an API key.`,
          inputSchema: {},
        },
        async () => {
          try {
            const result = await api.pricing();
            return successResult(result);
          } catch (err) {
            if (err instanceof ApiRequestError) return apiErrorToResult(err);
            return errorResult(err instanceof Error ? err.message : "Unknown error");
          }
        }
      );
  • Schema for get_pricing: inputSchema is empty (no input params), description describes the available credit packages.
      // --- get_pricing ---
      // No auth required
      server.registerTool(
        "get_pricing",
        {
          description: `Show available pipeline check credit packages and pricing. Returns all packages with credit counts and prices.
    
    Packages (one-time purchase, no subscription):
    - Starter: 100 credits for $9 ($0.09 each)
    - Standard: 500 credits for $39 ($0.078 each)
    - Pro: 2,000 credits for $99 ($0.0495 each)
    - Scale: 10,000 credits for $399 ($0.0399 each)
    
    Most URL lookups are free (known domains and cached domains). Credits are only consumed when an unknown domain runs through the full analysis pipeline. In typical use, 95-99% of URLs resolve free.
    
    This tool does not require an API key.`,
          inputSchema: {},
        },
        async () => {
          try {
            const result = await api.pricing();
            return successResult(result);
          } catch (err) {
            if (err instanceof ApiRequestError) return apiErrorToResult(err);
            return errorResult(err instanceof Error ? err.message : "Unknown error");
          }
        }
      );
  • The registerBillingTools function that registers get_pricing (along with get_balance and purchase) on the MCP server.
    export function registerBillingTools(
      server: McpServer,
      api: UnphurlAPI
    ): void {
  • src/index.ts:38-38 (registration)
    Top-level registration call: registerBillingTools(server, api) wires up get_balance, get_pricing, and purchase tools.
    registerBillingTools(server, api); // get_balance, get_pricing, purchase
  • The api.pricing() method called by the handler — makes a GET request to /v1/pricing (public, no auth needed).
    async pricing(): Promise<PricingResponse> {
      return this.doRequest<PricingResponse>("GET", "/v1/pricing");
    }
Behavior4/5

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

Without annotations, the description carries full burden. It explains what the tool returns (packages, credit counts, prices) and provides insight into credit consumption behavior (most lookups free). This adds valuable behavioral context beyond the empty schema.

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?

Description is well-structured with a summary sentence followed by a bulleted list of packages. It is somewhat lengthy but every sentence provides useful information. Could be slightly more concise but remains clear.

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

Completeness5/5

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

The description fully covers the tool's purpose and output (package list with credits and prices) without needing an output schema. It also includes practical details about credit consumption, making it complete for a simple listing tool.

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?

No parameters exist, and schema coverage is 100%. The description adds no param info, but baseline for zero-param tools is 4. It appropriately states the tool needs no API key.

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?

Description clearly states the tool shows available credit packages and pricing. It lists specific packages with counts and prices, making the purpose unambiguous. No sibling tool overlaps this functionality.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Description explains this is a read-only information tool and notes that most lookups are free, giving context for when to use it. It also clarifies no API key is needed. While it doesn't explicitly state when not to use it, the guidance is sufficient.

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/123Ergo/unphurl-mcp'

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