Skip to main content
Glama

Craft recipes

craft_recipes

Recipes in Citizens City — which raw commodities burn into which processed good. Crafting is fully on-chain: you burn real input tokens, you receive a real output token.

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

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 the full disclosure burden. It usefully explains that crafting is fully on-chain with real token burn and real token output, but the tool name 'craft_recipes' reads like an action verb, and the description never explicitly says this call only lists recipes and does not itself execute a craft — a materially important ambiguity for a zero-parameter mutation-adjacent name.

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?

Two short sentences with the subject front-loaded and no filler. The second sentence about on-chain burn/mint leans toward the crafting mechanic rather than this lookup tool, but it is brief enough to justify itself as context.

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?

There is no output schema and no annotations, so the description should at minimum sketch the return shape (a list of input-to-output recipe pairs) and note the related tool for actually performing a craft. It implies the former but leaves both partially unresolved, which is tolerable for a trivial zero-argument tool but not complete.

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 takes no parameters, so there is nothing for the description to disambiguate in the input schema. Baseline 4 applies; the description correctly avoids inventing filter semantics that the schema does not support.

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 states a concrete resource and its content shape: 'which raw commodities burn into which processed good' tells the agent this returns a recipe lookup table. It is clear on its own but never contrasts itself with the near-identical sibling craft_how_to or the commodity tools, so an agent must infer that this is the data and not the instructions.

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 when-to-use guidance, no exclusion, and no pointer to alternatives. The sibling list contains craft_how_to, commodity_markets, commodity_swap_build and forge, any of which an agent might plausibly pick instead, and the description does nothing to route between them.

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