Skip to main content
Glama

EcoGameWiki

by dev.carbonitex.ecogame

wiki_bom

Bill-of-materials for making a target item/recipe: the full crafting tree INCLUDING the crafted intermediate sub-components (NOT just raw leaves). This is the tool for 'how many does it take to make ' — including components the target never lists directly (they're summed transitively across the whole tree). Differs from wiki_total_raw (raw materials only) and wiki_calc (exact one-step numbers for a single recipe). Pass an item slug (uses its primary producing recipe) OR a recipe slug. Optional: quantity (units of the target, default 1, 1..10000); ingredient (a specific component name/slug — returns just that component's total quantity + whether it's an intermediate or raw); recipe_slug (override which producing recipe to use when the item has several — the others are listed as 'alternatives'). Optional character/server setup to recompute the whole tree: skill_level/skills, talents, modules/module, and server (model a different server's difficulty). Example: { slug:"steam-tractor", ingredient:"iron bar" } → how many iron bars a steam tractor needs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesThe TARGET item or recipe slug (from a wiki_search result).
moduleNoA single module name/type, or a comma-separated list (alternative to modules[]).
serverNoModel a DIFFERENT server by overriding its difficulty/feature settings (default = THIS server's real settings, so omit for accurate answers). Fields: craftResource (× ingredient cost), craftTime (× craft time), growth (× plant growth/maturity), garbageRatio (Update 14 craft-waste ratio, 0..1; scales recipe garbage byproducts), fuelEfficiency (× every fuel item's fuel value), foodVariety (bool), foodTastiness (bool), baseGain (flat XP/day floor), minBalanced/maxBalanced (balanced-diet multiplier range for food XP).
skillsNoPer-skill levels: { "<skill FullName>": level }. Overrides skill_level for those skills.
modulesNoUpgrade-module names/types installed (multiple slots stack).
talentsNoTalent names/types to treat as learned (applied across the whole chain). Their effect text is echoed back so you can explain why a number changed.
quantityNoHow many units of the target to produce (default 1; clamped 1..10000).
ingredientNoOptional: a specific component name or slug. Returns just that component's total quantity in the tree and its role (intermediate/raw).
recipe_slugNoOptional: when the target item has multiple producing recipes, pick this one (else the primary; others are reported as alternatives).
skill_levelNoA single skill level applied to EVERY governing skill in the chain (shortcut for a uniform setup).

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It thoroughly explains transitive summing, ingredient filtering, recipe alternatives, item-vs-recipe slug handling, skill/talent/server overrides, and echoed effect text. This goes far beyond a simple 'returns a BOM' statement.

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 dense but front-loaded with the core purpose and example. While it is a single long paragraph, it is well-structured and every sentence contributes necessary detail for a 10-parameter tool. Slightly more formatting (e.g., bullets) could improve scannability, but it remains highly functional.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is complex (10 params, nested server object, no output schema), and the description explains what the tool returns: total quantities, intermediate/raw status, alternatives, and echoed effect text. It does not describe the full response shape, but given the rich parameter documentation, it is complete enough for an agent to invoke correctly.

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?

Schema coverage is 100%, so baseline is 3. The description adds value by providing a concrete example ('steam-tractor', 'iron bar'), clarifying that slug can be an item or recipe, explaining that recipe_slug overrides the primary producing recipe, and noting that skill_level is a uniform shortcut. This meaningfully augments 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 tool as a full crafting-tree bill-of-materials generator, using a specific verb ('Bill-of-materials') and resource ('target item/recipe'). It explicitly differentiates from wiki_total_raw and wiki_calc by stating it includes intermediate sub-components and transitive sums, not just raw leaves.

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

Usage Guidelines5/5

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

The description gives explicit when-to-use guidance: 'This is the tool for how many <component> does it take to make <target>'. It also names alternatives and explains the difference, e.g., 'Differs from wiki_total_raw (raw materials only) and wiki_calc (exact one-step numbers for a single recipe)'.

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

All EcoGameWiki toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation2/5

search and wiki_search both perform full-text search over the Eco wiki and return similar ranked matches, making them easy to confuse. fetch and wiki_get also overlap as page-retrieval tools, though the crafting calculators are clearly differentiated.

Naming Consistency3/5

Most tools use a wiki_ prefix, but fetch and search break that pattern, and the suffixes are stylistically mixed (wiki_bom, wiki_calc, wiki_total_raw, wiki_contract_basics). The names remain readable and consistently lowercase snake_case, so the inconsistency is moderate rather than chaotic.

Tool Count4/5

Ten tools is a reasonable size for a wiki server covering search, retrieval, structured facts, numeric analysis, and crafting calculations. The count is slightly padded by the duplicate search tools and overlapping retrieval tools, but it is not excessive.

Completeness5/5

The tool set covers browsing, full-text search, structured entity facts, ranking, aggregation, multiple crafting-depth views, and gameplay mechanics like contracts. There are no obvious read-side dead ends, and write operations are appropriately absent for a wiki reference server.

Resources