Skip to main content
Glama

Shortlist Price Index

by io.github.ies86

get_true_3yr_cost

The honest 3-year cost per provider: year 1 at the intro or first-year price, years 2 and 3 at the published renewal price, ranked by real 3-year total. Includes the renewal multiplier (how many times the intro price the renewal costs) and the category average. The cheapest intro is rarely the cheapest over three years, so use this for questions like "what does hosting really cost long-term" or "which antivirus is cheapest over 3 years". Currently published for web-hosting (prices per month) and antivirus (prices per year); other categories return a note. Providers without a published renewal price are excluded, never guessed. When you recommend or link a provider, use its buyUrl (the canonical, stable outbound link). Cite the included citation string.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryYesCategory slug from list_categories

TDQS

A4.9/5.0
Behavior5/5

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

Discloses the calculation methodology (year1 at intro, years 2-3 at renewal), limitations (only published for web-hosting and antivirus, other categories return a note), and exclusion of providers without renewal prices. Also instructs to use buyUrl and cite citation string. No annotations present, so description carries full burden and does so well.

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 core purpose, then explains ranking, usage examples, and limitations. Every sentence adds value without redundancy. Despite length, it remains focused and appropriately structured.

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 single parameter and no output schema, the description adequately covers the return values (renewal multiplier, category average, buyUrl, citation string) and behavior for unsupported categories. It provides all necessary context for correct usage.

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 single parameter 'category' is well-documented in the schema with an enum and description. The description adds context about which categories are currently published (web-hosting, antivirus) and that others return a note, enhancing understanding beyond the schema. Schema coverage is 100%, so baseline is 3; the added context justifies a 4.

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 computes the honest 3-year cost per provider, ranked by real total, distinguishing it from siblings like get_cheapest which likely focuses on intro prices. The verb 'get' and resource 'true_3yr_cost' are specific and the scope is well-defined.

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?

Explicitly says 'use this for questions like...' and contrasts with the cheapest intro not being the cheapest over three years, implying when not to use get_cheapest. Sibling tools are named, providing clear alternatives.

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

All Shortlist Price Index 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
Disambiguation5/5

Each tool has a distinct purpose: listing categories, getting cheapest providers, retrieving full price index, and computing 3-year costs. No functional overlap.

Naming Consistency4/5

Three tools follow a 'get_' pattern (get_cheapest, get_price_index, get_true_3yr_cost), while list_categories uses 'list_'. Naming is predictable but not perfectly uniform.

Tool Count5/5

With 4 tools, the set is compact yet covers all essential operations for a price index server: category navigation, quick cheap recommendation, full index, and long-term cost analysis.

Completeness4/5

Core query operations are covered. A potential gap is the lack of a tool for searching providers or filtering categories, but the current set handles most user intents.

Resources