Skip to main content
Glama
SaltfishSheep

Native MC Mapping MCP Server

Search Native MC Access

search
Read-onlyIdempotent

Find deobfuscated equivalents for obfuscated Minecraft class, method, and field names across 38 versions using boolean query expressions and column filters.

Instructions

Search Minecraft obfuscated↔deobfuscated name mappings (classes/methods/fields).

expression syntax: term — case-insensitive substring term:modifier — substring match in column; term::modifier — exact match in column a&b (AND) | a|b (OR) | {expr} (grouping). & has higher precedence than |. "net.minecraft.Entity" auto-expands to "/" and "$" paths. Cross-version tip: "Player&Entity" works better than "EntityPlayer".

Modifiers: all (default) — all columns class — obf_class, deobf_class (full path) classname — class name after last '/' package — package before last '/' name — obf_name, deobf_name, srg_name (methods+fields) method — same columns, methods only field — same columns, fields only desc — obf_desc, deobf_desc modifier — access, is_static side — sideonly (common/server/client)

Scoring: exact case hit = 1.0, case-insensitive = 0.5, then by mismatch (less unmatched chars ranks higher).

Common patterns: "Entity::classname" → exact class name only "Gui:classname" → all classes containing "Gui" "net/minecraft/inventory:package" → all classes under a package "health:field" → fields only, no methods "()Z:desc" → methods returning boolean "get:method&static::modifier" → static methods containing "get" output="%deobf_class%" → deduplicated class list

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mc_versionYesMinecraft version to search (e.g. "1.12.2", "1.20.1"). Supported: 1.10.2, 1.11, 1.11.2, 1.12.2, 1.13, 1.13.1, 1.13.2, 1.14, 1.14.1, 1.14.2, 1.14.3, 1.14.4, 1.15, 1.15.1, 1.15.2, 1.16.1, 1.16.2, 1.16.3, 1.16.4, 1.16.5, 1.17, 1.17.1, 1.18, 1.18.1, 1.18.2, 1.19, 1.19.1, 1.19.2, 1.19.3, 1.19.4, 1.20, 1.20.1, 1.7.10, 1.8, 1.8.8, 1.8.9, 1.9, 1.9.4
expressionYesBoolean search expression (case-insensitive, exact case match scores higher). Syntax: term, term:modifier (substring match in column), term::modifier (exact match in column), a&b (AND), a|b (OR), {expr} (grouping with braces). Modifiers: all, class, classname, package, name, method, field, desc, modifier, side. & has higher precedence than |. Examples: "Entity::classname", "walk:method&static::modifier", "net/minecraft/entity:package"
pageNoPage number (1-indexed). Default: 1
limitNoNumber of results per page (default: 20, max: 100)
outputNoOutput format template using %variable% syntax (case-insensitive). Variables: %type%, %obf_class%, %obf_name%, %deobf_class%, %deobf_name%, %srg_name%, %obf_desc%, %deobf_desc%, %access%, %is_static% (static/non-static), %sideonly%, %match%, %mismatch%. Consecutive spaces collapsed. Identical outputs deduplicated.[%type%] %obf_class%/%obf_name% -> %deobf_class% %deobf_name% %srg_name% %obf_desc% %deobf_desc% %access% %is_static% %sideonly%
Behavior5/5

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

Annotations already provide readOnlyHint, destructiveHint, and idempotentHint. The description adds rich behavioral details: scoring algorithm, deduplication, output format variables, and expression semantics. No contradictions; the description significantly augments understanding beyond annotations.

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 well-organized into sections (syntax, modifiers, scoring, common patterns, output). It is front-loaded with the main purpose. Every part adds value given the tool's complexity, though some minor trimming might be possible.

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?

With no output schema, the description explains return values via scoring, deduplication, and output format templates. It covers search behavior, syntax, and common patterns comprehensively. However, it doesn't explicitly describe the exact structure of a result item beyond the template, so slightly incomplete.

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 description coverage is 100%, so baseline is 3. The description provides additional context for parameters like expression syntax and output template variables with examples, which enhances understanding without being essential. It adds value but not critical new semantics.

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 states the tool searches 'Minecraft obfuscated↔deobfuscated name mappings (classes/methods/fields)', providing a specific verb and resource. Since there are no sibling tools, differentiation is not needed, but the purpose is unmistakable.

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?

The description includes extensive syntax guidance, modifiers, scoring details, and common patterns, effectively showing how to use the tool. It offers cross-version tips and template usage. However, it does not explicitly state when not to use it or compare to alternatives, though no siblings exist.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SaltfishSheep/AI-MCP-NativeMinecraftAccess'

If you have feedback or need assistance with the MCP directory API, please join our Discord server