Skip to main content
Glama

Rank drinks

rank_drinks
Read-only

Rank drinks by calories, sugar, carbs, Hangover Index or ABV, optionally filtered, e.g. lowest calorie gluten-free hard seltzer. Drinks with no verified figure are left out.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "metric": "<metric>"
    },
    "name": "rank_drinks"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoResults to return. Default 10.
orderNoDefault lowest.
veganNo
familyNo
metricYes
categoryNoA category such as "vodka" or "hard-seltzer".
glutenFreeNoOnly drinks gluten-free under US labelling rules.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, closed-world, non-destructive safety. The description adds genuinely useful behavior beyond them: "Drinks with no verified figure are left out" tells the agent results are silently truncated for missing data, which affects how results should be interpreted and reported. It doesn't cover pagination or return shape, but that is secondary here.

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?

Two tight sentences: capability and metrics first, then a concrete example, then the caveat about missing data. Nothing is padded or repeated.

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

Completeness4/5

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

For a 7-parameter read tool with no output schema and annotations covering safety, the description supplies metrics, filterability, and the omission caveat. Only minor gaps remain (limit ceiling, family/vegan semantics), all of which happen to be partly defined by enums or schema descriptions.

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?

Schema coverage is 57%, so the description carries real weight. It enumerates the metric values in prose (including the domain-specific "Hangover Index") and signals that filters are optional via a concrete example combining order, metric and gluten-free. It doesn't explain 'family', 'vegan', or the 50-result cap, leaving some gap.

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?

Specific verb+resource ("Rank drinks") with the exact metrics available (calories, sugar, carbs, Hangover Index, ABV) and the filterable nature of the operation. It doesn't explicitly distinguish itself from siblings like compare_drinks or search_drinks, but the verb 'rank' versus 'compare' or 'search' is naturally discriminating.

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 example ("lowest calorie gluten-free hard seltzer") implies the use case and shows how metric + filter combine, but there is no explicit routing guidance - nothing says when to use this instead of search_drinks or compare_drinks.

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.

Resources