Skip to main content
Glama

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. For a placed object this INCLUDES its measurements — storage slots and weight capacity, storage link range, interact distance, power-grid radius, footprint and top speed — so read the page before saying a size/range/capacity isn't tracked. • 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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYes1–12 pages to read in one call.

TDQS

A5/5.0
Behavior5/5

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

With no annotations provided, the description fully discloses behavior: it is a read operation, it can return multiple pages, and ambiguous slugs return all matches. It also details what facts are included for each kind, even warning that placed-object measurements are included so the agent does not assume they are missing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but every sentence earns its place given the domain complexity. The core purpose and batching advice are front-loaded, followed by a structured breakdown of kinds and a clear fallback instruction for omitting 'kind'.

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

Completeness5/5

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

With no output schema, the description provides a comprehensive account of what the tool returns and how to call it correctly. It covers all input combinations, explains edge cases, and gives enough domain-specific detail that an agent can select appropriate parameters without guessing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Though the schema already describes the parameters, the description greatly enriches their meaning. It explains each 'kind' value in detail (item, recipe, skill, category, species, biome), says the slug should come from wiki_search, and clarifies batching semantics and the fallback behavior for ambiguous slugs.

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 uses a specific verb ('Read full facts') and resource ('wiki pages'), and clearly defines the tool's scope: retrieving full page contents for one or many pages in a single call. It also distinguishes itself from related tools by explicitly naming wiki_calc and wiki_total_raw as alternatives for exact modified numbers and from-scratch chains.

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 usage guidance: batch all needed pages, obtain slugs from wiki_search, and omit 'kind' only if unsure. It also specifies alternatives for recipe calculations (wiki_calc, wiki_total_raw), providing clear when-to-use and when-not-to-use context.

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.

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