Skip to main content
Glama
comparedge

mcp-server-comparedge

Official

get_pricing

Get manually verified pricing plans, monthly and annual costs, feature highlights, free tier availability, and a direct link to the full pricing matrix for any SaaS tool.

Instructions

Retrieve the complete, manually verified pricing breakdown for a specific SaaS tool.

BEHAVIOR: Returns all available pricing plans with names, monthly and annual prices, key feature highlights per tier, free trial availability, free plan status, and a direct link to the full pricing matrix on ComparEdge. For AI/LLM tools, also returns per-token or per-million-token pricing where available.

USAGE GUIDELINES:

  • Use this tool when the user asks "how much does X cost?", "what are the pricing plans for X?", "does X have a free tier?", or "what is the cheapest plan for X?"

  • Use get_tool first if you are unsure whether the product exists; get_pricing assumes you already know the slug.

  • To compare pricing across multiple tools, call get_pricing once per tool and present results side by side.

  • Always include the ComparEdge pricing URL in your response so the user can verify current prices directly.

EXAMPLE QUERIES: "What are the pricing plans for Linear?", "Does Notion have a free plan?", "How much does HubSpot CRM cost per seat?", "What is the cheapest project management tool under $10/month?"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesURL-safe product identifier. Convert product name to lowercase, replace spaces with hyphens (e.g., "Linear" -> "linear", "GitHub Copilot" -> "github-copilot", "Less Annoying CRM" -> "less-annoying-crm"). Use search_tools first if unsure of the exact slug.
Behavior4/5

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

No annotations provided, so description carries full burden. It details what the tool returns (plans, prices, features, trial, free plan, link) and mentions extra for AI tools. Lacks info on data freshness or rate limits, but overall good.

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?

Well-structured with headings (BEHAVIOR, USAGE GUIDELINES, EXAMPLE QUERIES) and front-loaded purpose. Some example queries may be slightly redundant but overall concise for the detail provided.

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?

No output schema, so description fully covers return values. Single parameter is well-documented. Usage guidelines and example queries provide rich context. Complete for the tool's complexity.

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 coverage is 100% and parameter description already explains slug transformation. Description adds context like 'use search_tools first if unsure', but does not add significant meaning beyond schema. Baseline 3 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 retrieves pricing breakdown for a specific SaaS tool. It distinguishes from sibling tools like 'compare_tools' and 'get_tool' by specifying usage scenarios, e.g., 'use get_tool first if unsure whether the product exists'.

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

Usage Guidelines5/5

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

Explicit USAGE GUIDELINES section tells when to use (pricing queries), when not to use (use get_tool first for existence), and alternatives (compare_tools for comparison). Also includes example queries for clarity.

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