Skip to main content
Glama
Sign In
Brewers almanack

Brewers almanack

by gregario
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Check GEB Stock

check_geb_stock

Check GetErBrewed.com kit builder inventory for ingredient availability and pricing, and get substitution suggestions when items are out of stock.

Instructions

Check GetErBrewed.com custom kit builder inventory for ingredient availability and pricing. Data is updated weekly. If an item is out of stock, suggests substitutions.

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": {
      "query": "<query>"
    },
    "name": "check_geb_stock"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesIngredient to search for (e.g. 'Citra', 'Maris Otter', 'US-05')
categoryNoFilter by category (e.g. 'T90 Hops', 'Base Malt', 'Dried Yeast')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.3

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavior fully. It mentions weekly data updates and substitution suggestions, but lacks details on pricing output, authentication needs, rate limits, or error handling. The description does not specify the response format or what happens when an ingredient is not found.

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 concise with two sentences. The first sentence immediately states the purpose, and the second adds key details about data freshness and substitution behavior. No unnecessary words.

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?

For a simple tool with two parameters and no output schema, the description covers the basic purpose and behavior. However, it does not describe the output format or what happens when a query returns no results. Given the lack of output schema, more detail on return structure would improve completeness.

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 coverage is 100%, so baseline is 3. The description adds context about ingredient availability and pricing but does not add semantic meaning beyond the schema descriptions for query and category. Parameters are well-documented in schema, so description adds minimal extra value.

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 verb 'Check' and the resource 'GetErBrewed.com custom kit builder inventory for ingredient availability and pricing.' It distinguishes from sibling tools like search_ingredients by specifying the website and including stock checking and substitution suggestions.

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 description implies usage for checking stock and getting substitutions but does not explicitly state when to use this tool versus alternatives like suggest_substitution or search_ingredients. No exclusions or prerequisites are mentioned.

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

Deploy Server

Other Tools