Skip to main content
Glama

Mojang

by io.github.pipeworx-io

Discover Tools

discover_tools
Read-onlyIdempotent

Find tools by describing the data or task. Use when you need to browse, search, look up, or discover what tools exist for: SEC filings, financials, revenue, profit, FDA drugs, adverse events, FRED economic data, Census demographics, BLS jobs/unemployment/inflation, ATTOM real estate, ClinicalTrials, USPTO patents, weather, news, crypto, stocks. Returns the top-N most relevant tools with names, descriptions, and full input schemas (with curated examples) — each result is ready to call directly, no second schema lookup needed. Call this FIRST when you have many tools available and want to see the option set (not just one answer).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoAlias for query.
taskNoAlias for query.
limitNoMaximum number of tools to return (default 20, max 50)
queryYesNatural language description of what you want to do (e.g., "analyze housing market trends", "look up FDA drug approvals", "find trade data between countries"). Accepts task, q, description, search as aliases.
searchNoAlias for query.
descriptionNoAlias for query.

Schema Changelog

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

  1. Changed6 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "look up FDA drug approvals"
+  },
+  {
+    "query": "analyze housing market trends"
+  }
+]
    • addedInput schema / properties / description
      Added value: +{
+  "description": "Alias for query.",
+  "type": "string"
+}
    • addedInput schema / properties / q
      Added value: +{
+  "description": "Alias for query.",
+  "type": "string"
+}
    • changedInput schema / properties / query / description
      Previous value: -"Natural language description of what you want to do (e.g., \"analyze housing market trends\", \"look up FDA drug approvals\", \"find trade data between countries\")"New value: +"Natural language description of what you want to do (e.g., \"analyze housing market trends\", \"look up FDA drug approvals\", \"find trade data between countries\"). Accepts task, q, description, search as aliases."
    • addedInput schema / properties / search
      Added value: +{
+  "description": "Alias for query.",
+  "type": "string"
+}
    • addedInput schema / properties / task
      Added value: +{
+  "description": "Alias for query.",
+  "type": "string"
+}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context about the output: it returns top-N tools with names, descriptions, full input schemas, and curated examples, ready to call directly with no second lookup. This goes beyond the annotations and clarifies the interaction model.

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 four sentences and front-loaded with the core purpose. Each sentence has a distinct role: purpose, usage context, output behavior, and when-to-call guidance. The lengthy domain list is somewhat dense but serves as concrete examples of intended queries, so it earns its place. It is slightly longer than necessary, preventing a 5.

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?

The tool is a discovery meta-tool with no output schema, but the description fully explains what the return value looks like: top-N tools with names, descriptions, full schemas, and curated examples, ready for direct invocation. It also covers when to use it and the kinds of tasks it supports. Given the tool's complexity and the rich schema, the description is complete enough for an agent to invoke it correctly.

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 description coverage is 100%, and the schema thoroughly documents all six parameters including aliases and the limit parameter with defaults. The description adds general guidance about natural-language queries and the result set, but it does not meaningfully improve parameter-level understanding beyond what the schema already provides, so the baseline of 3 applies.

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+resource pair: 'Find tools by describing the data or task.' It clearly distinguishes this tool as a meta-discovery tool for browsing the available option set, unlike the many domain-specific sibling tools. The list of supported domains further clarifies its scope.

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 explicitly states when to use it: 'Use when you need to browse, search, look up, or discover what tools exist' and 'Call this FIRST when you have many tools available.' It gives clear context and an implied exclusion ('not just one answer'), but it does not explicitly name alternative tools or state when not to use it, so it falls just short of 5.

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