Skip to main content
Glama

Get drink facts

get_drink
Read-onlyIdempotent

Full label facts for one drink identified by its EDR slug: caffeine, sugar, calories, serving size, sweetener and flavor info, availability, the community rating with its count and, when there are enough written reviews, a one-line summary of what raters say. Also returns links to the drink page, to rate the drink and to a free caffeine tracker.

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": {
      "slug": "<slug>"
    },
    "name": "get_drink"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe drink's EDR slug, e.g. 'bang-purple-haze'

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?

The annotations already declare readOnlyHint=true and idempotent, so the description appropriately focuses on return value details: it lists the specific facts returned, notes that the community summary only appears when there are enough reviews, and mentions included links. This adds useful behavioral context beyond the structured fields.

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 a single, front-loaded sentence that efficiently lists the returned information. Every element earns its place, with no redundancy or wasted words.

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?

For a simple single-parameter tool with no output schema, the description is complete: it fully describes what data is returned, including conditional elements (community summary) and links. An agent has everything needed to understand the tool's output.

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?

The schema description coverage is 100% and the single parameter 'slug' is fully documented in the schema. The description adds the term 'EDR slug' but no additional syntax or format details beyond what the schema provides, so it meets the baseline.

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 clearly states it returns 'full label facts for one drink identified by its EDR slug' and enumerates the data fields, making it easy to distinguish from multi-drink siblings like search_drinks. However, it does not explicitly name those siblings to reinforce the differentiation.

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?

Usage is implied: use this tool when you have a specific drink slug and need detailed facts. There is no explicit guidance on when to use it versus alternatives like compare_drinks or search_drinks, nor any exclusions.

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