Skip to main content
Glama

Mojang

by io.github.pipeworx-io

Remember

remember
Idempotent

Save data the agent will need to reuse later — across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved ticker, a target address, a user preference, a research subject) so you don't have to look it up again. Stored as a key-value pair scoped by your identifier. Authenticated users get persistent memory; anonymous sessions retain memory for 24 hours. Pair with recall to retrieve later, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesMemory key (e.g., "subject_property", "target_ticker", "user_preference")
valueYesValue to store (any text — findings, addresses, preferences, notes)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Adds valuable behavioral context beyond annotations: persistence scoped to identifier, 24-hour retention for anonymous sessions, and key-value pairing. No contradictions with annotations (idempotent, non-destructive). The only missing detail is explicit overwrite behavior, but idempotentHint already covers that.

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?

Four sentences, each earning its place: purpose, usage, storage mechanics, and companion tools. No filler or redundancy; front-loaded with the core action.

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?

For a two-parameter tool with no output schema and comprehensive annotations, the description covers all essential aspects: purpose, when to use, persistence, scoping, and relationships to sibling tools. Nothing critical is missing.

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

Parameters3/5

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

Schema covers 100% of parameters with clear descriptions, so the description adds little beyond that. It reinforces key-value semantics with examples, but these largely mirror the schema's own examples, providing no significant additional meaning.

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 saves data for later reuse with specific verb ('Save') and resource ('data'), and distinguishes it from siblings by explicitly pairing with recall and forget. Examples of what to store (resolved ticker, target address) make the purpose unmistakable.

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?

Provides explicit 'Use when' guidance with concrete scenarios, and names alternatives (recall, forget) with their roles. This gives clear direction on when to invoke this tool versus other memory-related tools.

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

All Mojang 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.7/5.0
Disambiguation2/5

ask_pipeworx and ask_pipeworx_beta are currently described as functionally identical, creating a clear misselection risk, and several query/answer tools (ask_pipeworx, ask_pipeworx_grounded, deep_research, validate_claim, entity_profile, compare_entities) have overlapping boundaries. The Polymarket tools also blur into each other, so despite verbose descriptions, an agent can easily route a request to the wrong tool.

Naming Consistency3/5

All names are snake_case and readable, but the conventions are mixed: verb_noun (ask_pipeworx, resolve_entity), noun_noun (entity_profile, bet_research), bare verbs (remember, recall, forget, profile), and prefix families with inconsistent ordering (ask_pipeworx vs pipeworx_feedback, polymarket_edges vs polymarket_kalshi_spread). This is not chaotic, but there is no single predictable naming pattern.

Tool Count2/5

36 tools is well past the 25+ threshold for a heavy surface, and the server name 'Mojang' implies a narrow Minecraft API scope while only 5 tools relate to Minecraft. The rest belong to a broad data-research, prediction-market, and memory platform, making the tool count feel inflated and mis-scoped for the server's stated identity.

Completeness2/5

For the implied Minecraft/Mojang domain, there are obvious gaps such as no authentication, skin/name mutation, or broader account endpoints, so that surface is thin. Meanwhile, the Pipeworx data side is fairly complete, but because two unrelated domains are jammed into one server, neither domain is covered in a coherent, trustworthy way.

Resources