Skip to main content
Glama

Savings leaderboard

leaderboard
Read-onlyIdempotent

The top replacement paths across the catalog by modeled first-year savings, payback months, or how often people and agents used them. Leaves out partial replacements unless include_partial, and never lists trials, one-time credits, expiring or non-commercial plans. Stackcut stores the arguments of tool calls to improve its recommendations (vendor names, prices, seats, features, usage numbers, billing amounts and project descriptions; account keys only as a one-way hash, billing and validation sources not at all; never IP addresses). Tool results are summarized; exit tools log only result counts, qualification flags and public evidence statuses, not answer contents. Don't send personal data or secrets.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "leaderboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
metricNosavings
categoryNo
path_typeNo
include_partialNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / metric / maxLength
      Added value: +2000
    • addedInput schema / properties / path_type / maxLength
      Added value: +2000
  2. Changed2 schema fields changed
    • addedInput schema / properties / category / maxLength
      Added value: +100
    • addedInput schema / properties / category / minLength
      Added value: +1
  3. Changed1 schema field changed
    • changedInput schema / properties / path_type / enum
      Previous value: -[
      -  "switch",
      -  "downgrade",
      -  "open_source",
      -  "per_use",
      -  "build",
      -  "bundled"
      -]New value: +[
      +  "switch",
      +  "downgrade",
      +  "open_source",
      +  "per_use",
      +  "agent_skill",
      +  "build",
      +  "bundled"
      +]
  4. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint=false), so the bar is low, yet the description adds substantial detail: which result classes are never listed, that results are summarized/aggregated, and a detailed data-retention disclosure. It stops short of describing return shape or pagination, keeping it out of the top band.

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?

Purpose and scope are front-loaded in the first sentence, followed by exclusions then privacy. It is longer than typical due to the parenthetical data-handling detail, but every sentence is informative rather than filler.

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

Completeness3/5

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

With no output schema, the description should also characterize the return value; it names the ranking basis and exclusions but not the shape or fields of each returned path. Two enum-ish parameters (category, path_type) also go unexplained, leaving gaps for an agent assembling a call.

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 0% across 5 parameters, so the description carries the burden. It maps the metric enum values to human meanings (savings, payback months, usage frequency) and explains include_partial, but leaves category, path_type (7 enum values) and limit entirely unexplained. Partial compensation only.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb+resource: it returns 'the top replacement paths across the catalog' ranked by one of three metrics, which is a clear, concrete purpose. It does not name or differentiate itself against siblings like find_alternatives or search_exits, but the leaderboard/ranking concept is distinct enough to be inferable.

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

Usage Guidelines2/5

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

The description explains what is included or excluded from results (partial replacements, trials, one-time credits, expiring/non-commercial plans) but never says when to reach for this tool versus find_alternatives, search_exits, or choose_stack. No positive usage triggers or exclusions relative to alternatives are given.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.