Connect your agent to this wiki

This wiki is built to be read by AI agents, not just browsers. Every page is available as clean Markdown, the whole thing is described by standard discovery files, and a read-only tool server exposes search and deep lookups. This is anonymous and read-only by design: there is no login, no key, no write access, and no LLM behind the tool surface.

1 · Discover the surface

Point your agent at the site root and let standard discovery files do the work. All are anonymous GETs.

2 · Read pages as Markdown

是 Accept: text/markdown on any page request (or append ?format=md) to get the page as clean Markdown instead of HTML:

curl -H "Accept: text/markdown" https://ecogame.carbonitex.dev/wiki/item/iron-bar

3 · The read-only MCP server

A minimal MCP server (JSON-RPC 2.0 over HTTP) exposes https://ecogame.carbonitex.dev/mcp. It serves two primitives plus the full deterministic wiki tool set:

search

Full-text search (the FTS5 index behind the site's own search).

fetch

Fetch one page as Markdown by canonical path.

wiki_search

Full-text search the Eco game wiki (items, recipes, skills, categories, animals, plants, biomes). Returns matching pages with their kind, name, slug, and a snippet. Use the slug with the matching wiki_get_* tool to read full facts. ALWAYS search first to find the right slugs.

wiki_get

Read full facts for one OR MANY wiki pages in a single call. Pass every page you need at once (e.g. a recipe AND its ingredient items) — batching saves round-trips. Each entry takes a slug (from wiki_search) and, ideally, its kind: • item — item/food/tool/placed-object/block: description, category, tags, weight/stack, fuel, food nutrition + shelf life, tool/weapon stats, placed-object stats (housing, rooms, power/fuel, storage), block facts, where obtained, recipes that make/use it. • recipe — products (+waste), ingredients (specific items OR categories w/ examples), station, skill + level, labor, craft time, XP, throughput, and the levers that change the numbers. (wiki_calc for exact modified numbers; wiki_total_raw for the from-scratch chain.) • skill — tier, max level, prerequisites, recipes unlocked. • category — a tag's member items and the recipes that use it. • species — an animal OR plant/tree: description, yields; animals: diet/predator/nocturnal; plants: biomes, ideal temperature. • biome — the plants/trees that grow there. Omit kind only if unsure; an ambiguous slug returns all matches so you can re-request with the right kind.

wiki_total_raw

Flatten a recipe or craftable item to its TOTAL RAW materials across the whole production chain, with total labor calories, total craft minutes, and crafting-step count. Pass an item slug OR a recipe slug. Use for 'what does it take to make X from scratch' (the raw shopping list). For a breakdown that ALSO includes the crafted intermediate sub-components (e.g. how many iron bars), use wiki_bom instead. Optionally pass a character setup (skill_level/skills, talents, modules) AND/OR a server override to recompute the WHOLE chain for that profile.

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 <component> does it take to make <target>' — 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.

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).

wiki_contract_basics

Explain how Solomon's help contracts and quests work for players (the kinds available, how rewards/escrow work, how completion is verified). Use for 'how do contracts/quests work' questions.

wiki_rank

Rank the wiki's entities by a NUMERIC field and return the top (or bottom) N. Use this for ANY 'which has the most/least/highest/lowest X' question — never guess-and-confirm with wiki_search. Choose a kind, the field to rank 'by', order (desc = highest first, the default; asc = lowest first), an optional limit (default 5, max 25), an optional 'category' to scope to one tag (food/item/species only — e.g. category "seed"), and an optional numeric 'where' filter. Available fields by kind (a field that doesn't apply to a given entity — e.g. a tool stat on a non-tool — simply excludes it): • food: calories, carbs, fat, protein, shelf_life, stack, vitamins, weight • item (base + placed-object + tool + block facets): air_pollution, animal_damage, block_tier, calories_burn, damage, durability_burn, fertility, fuel, fuel_jps, grid_radius, hardness, harvest_yield, housing_value, is_fuel, is_mintable, is_road, is_weapon, labor_max, labor_min, max_coins, max_durability, move_efficiency, pollution, power_generated, power_watts, repair_level, room_tier, room_volume, school_value, seats, size_x, size_y, size_z, stack, storage_slots, storage_weight, tool_tier, vehicle_speed, weight • recipe: craft_minutes, crafting_steps, ingredients, labor, products, skill_level, skill_max_level, xp • skill: max_level, tier • species (animals ∪ plants/trees): attacks_player, calorie_value, co2_per_day, health, ideal_temp_max, ideal_temp_min, is_predator, nocturnal, yield_min_total, yield_total Bool fields read as 1/0 (e.g. where { field: "is_predator", op: "=", value: 1 }). Example: { kind: "food", by: "calories", order: "desc", limit: 3 } → the 3 highest-calorie foods. Scoped example: { kind: "food", by: "shelf_life", order: "asc", category: "seed" } → the seeds that spoil fastest. Optional character/server PROFILE (skill_level/skills, talents, modules/module, server) re-ranks the profile-sensitive metrics — recipe labor/craft_minutes; tool damage/calories_burn/durability_burn; item harvest_yield/power_watts; species yield_total/yield_min_total (craft_minutes also honors server craftTime). All other fields are static facts and ignore the profile (the result carries a note). No profile = base ranking.

wiki_aggregate

Compute an aggregate over the wiki's entities — count / sum / avg / min / max of a numeric field across a whole kind, with an optional numeric 'where' filter. Use for 'how many…', 'what's the average/total/highest…' questions. 'count' needs no field (counts entities, or those matching 'where'); sum/avg/min/max require a 'field'. Supports the same optional 'category' scope as wiki_rank (food/item/species). Kinds and field names are the SAME as wiki_rank — see that tool's per-kind field lists. Example: { kind: "recipe", metric: "count", where: { field: "skill_level", op: ">", value: 5 } } → how many recipes need skill level above 5. Scoped: { kind: "food", metric: "avg", field: "calories", category: "vegetable" } → average calories of vegetables. Optional character/server PROFILE (skill_level/skills, talents, modules/module, server) recomputes the same profile-sensitive metrics as wiki_rank (recipe labor/craft_minutes; tool damage/calories_burn/durability_burn; item harvest_yield/power_watts; species yield_total/yield_min_total); static fields ignore it (the result carries a note). No profile = base aggregate.

POST https://ecogame.carbonitex.dev/mcp
Content-Type: application/json

{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}

Handshake example: initialize → tools/list → tools/call. The server card lists the endpoint.

4 · WebMCP (in the browser)

When this page is open in a browser that supports the WebMCP spec, it registers the wiki's tools with the browser (document.modelContext.registerTool) — so the browser's own agent can search and read the wiki without leaving the page. That's entirely client-side and needs no configuration.

5 · Flat HTTP tool endpoint

Scripting agents that skip MCP can call the same deterministic tools directly:

POST https://ecogame.carbonitex.dev/wiki/api/tool
Content-Type: application/json

{"name":"wiki_get","arguments":{"items":[{"slug":"iron-bar","kind":"item"}]}}

Available tool names: wiki_search, wiki_get, wiki_total_raw, wiki_bom, wiki_calc, wiki_contract_basics, wiki_rank, wiki_aggregate

Prefer a human-style conversation? Ask Solomon &rarr;