Skip to main content
Glama

Unphurl

by io.github.123Ergo

get_pricing

Read-onlyIdempotent

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

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds useful behavioral context beyond these annotations, such as 'This tool does not require an API key' and the explanation of when credits are consumed (only for unknown domains). This enriches the agent's understanding of the tool's behavior and domain context.

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 front-loaded with the main purpose, then presents the package list in a clear bullet-point format, followed by crucial usage details about free lookups and API key requirements. Each sentence earns its place; no unnecessary filler or redundancy.

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?

Given the tool's simplicity (no parameters, no output schema), the description is fully complete. It explicitly lists all packages with credit counts and prices, explains the credit consumption model, and notes the absence of an API key requirement. This is sufficient for an agent to understand the tool's behavior and return value without needing a formal output schema.

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 tool has zero parameters, so the schema gives no parameter information. With 0 params, the baseline is 4. The description doesn't need to explain parameters and instead focuses on the return content, which is appropriate.

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 tool's purpose: 'Show available pipeline check credit packages and pricing' and 'Returns all packages with credit counts and prices.' This is a specific verb+resource that distinguishes it from siblings like get_balance (which probably shows current balance) and purchase (which actually buys credits).

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 by listing pricing packages and noting that credits are only consumed for unknown domains, but it does not explicitly state when to use this tool vs alternatives like get_balance or purchase. No when-not or direct alternative comparisons are provided, so it relies on implied context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Unphurl toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation4/5

Most tools have clearly distinct purposes: check_url vs check_urls distinguish single vs batch, allowlist CRUD tools are separated, and profile management is distinct from account billing. Minor overlap exists between get_balance and get_stats (both report balance) and between list_profiles and show_defaults (both relate to scoring configuration), but descriptions clarify the differences.

Naming Consistency4/5

The vast majority of tools follow a verb_noun snake_case pattern (check_url, create_profile, list_allowlist, get_balance). A few outliers like purchase and signup are single verbs, but they are standard and do not break the overall predictability.

Tool Count4/5

18 tools is above the ideal 3-15 range but appropriate for the server's broad scope: URL analysis, custom scoring profiles, allowlist management, account billing, and reporting. Each tool serves a distinct function and none feel redundant or superfluous.

Completeness4/5

The tool surface covers the core domain thoroughly: single and batch URL checks, credit estimation, profile CRUD (create, list, delete, show defaults), allowlist CRUD, history, and account management (signup, balance, pricing, purchase). Minor gaps exist, such as no delete history or direct retrieval of a single past check by ID, but these are not critical.

Resources