Skip to main content
Glama

Get drink facts

get_drink
Read-only

Full facts for one drink or category: nutrition per serving, seven chemistry factors (congeners, histamines, polyphenols, sulfites, tannins, sugar, additives), allergens, gluten and vegan status, sourcing notes.

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

Input Schema

NameRequiredDescriptionDefault
drinkYesA brand or a category such as "gin".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

The description goes far beyond what annotations provide by enumerating the exact data points included, such as 'seven chemistry factors,' 'allergens,' and 'sourcing notes.' This informs the agent precisely what kind of data and behavioral payload to expect from this resource.

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, focused paragraph. It is front-loaded with the main purpose ('Full facts') and then efficiently lists the contents, using minimal words to describe a vast set of information.

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 that there is no output schema, the description is nearly perfect. It serves as a comprehensive contract, listing all the granular details (nutrition, specific factors) that an agent needs to understand the utility of this tool.

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?

Since schema description coverage is 100%, the description is highly redundant regarding parameter meaning. It merely reinforces that the input should be a single entity ('drink or category') as already documented in the schema.

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 defines the action ('Get Full facts') and the object ('one drink or category'). By specifying 'one' versus the broader search and list siblings, it leaves no doubt about the tool's specific scope.

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

Usage Guidelines4/5

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

It defines the context of use as retrieving 'full facts' for a singular entry. It implicitly sets it apart from search tools (which imply a list) and list tools (which focus on categories), though it does not explicitly state 'use this when' or 'do not use this when'.

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