Skip to main content
Glama

ingredient_catalog

List Apothecary ingredients with price in KARMABUX per unit (also available as karmaValue), recipes with karmaCost brewing fees, positive-quantity ingredients you own, and your active potion effects.

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": "ingredient_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries full behavioral burden. It usefully discloses filtering behavior ('positive-quantity ingredients you own' and 'active potion effects') and field meanings, but does not explicitly confirm read-only behavior, pagination, or any side effects/error conditions for this listing operation.

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?

The description is a single front-loaded sentence with no filler, and every clause conveys a distinct category of returned data. It is dense and slightly run-on, but still efficient and appropriately sized for a zero-parameter listing tool.

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?

The description adequately states what categories are included, which is the main context needed to call a zero-parameter read tool. However, without an output schema or annotations, it does not describe the return structure (for example whether categories are separate arrays or one combined payload), leaving a meaningful completeness gap.

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?

The tool has zero input parameters, so there are no parameter semantics for the description to clarify. The baseline score of 4 applies.

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 uses a specific verb ('List') and names the concrete resources: Apothecary ingredients with KARMABUX pricing, recipes with brewing fees, owned positive-quantity ingredients, and active potion effects. It is clear what data the tool returns, though it does not explicitly distinguish this multi-resource catalog from siblings such as catalog, kitchen_recipes, or inventory.

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?

There is no explicit when-to-use guidance, no exclusions, and no mention of alternatives such as catalog, inventory, or kitchen_recipes. The bundled content implies it is for browsing shop ingredients and related recipe/potion data, but the description leaves the agent to infer that.

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