Skip to main content
Glama

EcoGameWiki

by dev.carbonitex.ecogame

wiki_calc

Compute EXACT numbers for a chosen setup. For a RECIPE: labor calories, craft time, per-ingredient counts and throughput at a given skill level + upgrade module + talents. For a FOOD item: its STATIC calories/nutrition (eating never changes these) PLUS an estimated XP / skill-gain rate from the diet inputs (balanced/variety/tastiness/housing). For a TOOL/WEAPON: damage, calories-per-use, durability-per-use at the tool's governing-skill level + talents. For a MINEABLE BLOCK: per-block calorie/durability cost (for a representative pickaxe), yield, and calories-per-stack at a mining-skill level + talents. For a SPECIES: harvest yields recomputed with the reader's harvest-yield talents. Omit a lever to leave it at base; the response lists the available modules/talents/skill (with each talent's effect text) so you can pick valid ones and explain what changed. Optional 'server' override models a different server's difficulty (recipes honor craftResource/craftTime; mining/species honor their relevant settings; food honors foodVariety/foodTastiness).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesA recipe, food-item, or species slug (from wiki_search).
moduleNoUpgrade-module name or tier number (recipes only); lowers craft time/materials.
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).
housingNoFood only: your housing XP contribution (additive to the skill-gain rate; default 0).
talentsNoTalent names to treat as learned (recipes/tools/mining/species yields).
varietyNoFood only: your current food-variety bonus multiplier (default 1).
balancedNoFood only: assume a balanced diet (max balanced-diet bonus) vs this food alone.
tastinessNoFood only: your current food-tastiness bonus multiplier (default 1).
skill_levelNoGoverning-skill level (recipes/tools/mining); lowers labor / tunes stats.

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations, the description fully carries the burden and excels: it discloses computation scope per item type, clarifies that food stats are static, and explains that the response lists available modules/talents/skill. It also details server override behavior, providing rich context beyond the schema.

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 lengthy but necessarily so, covering multiple item types. It is front-loaded with the core purpose and organized by item type with clear sections. There is no fluff, though the density could be slightly reduced with tighter formatting.

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?

Despite lacking an output schema, the description explains what the response includes (available modules/talents/skill with effect text) and covers all item categories and parameter roles. It stops short of a sample return, but for a complex calculator it is quite 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?

Schema coverage is 100%, so baseline is 3. The description adds meaningful context by explaining how parameter groups apply (skill_level+module+talents for recipes, housing/variety/balanced/tastiness for food, server overrides for specific settings) and notes that omitting a lever leaves it at base, which goes beyond 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 states a specific verb ('Compute EXACT numbers') and identifies the exact resource types (recipes, food, tools, blocks, species), clearly distinguishing it from search/aggregate sibling tools. It leaves no ambiguity about what the tool does.

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 provides clear context for when to use the tool—whenever exact calculated numbers are needed for the enumerated item categories. It does not explicitly name alternatives like wiki_get or wiki_total_raw, but the exhaustive categorization implicitly guides appropriate use.

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