Skip to main content
Glama

uselessfacts

by io.github.pipeworx-io

Random Fact

random_fact
Read-onlyIdempotent

Return one random trivia fact in English from the Useless Facts API at uselessfacts.jsph.pl. Returns the fact text with its id, the attributed source name, source URL, and a permalink. Use it for an amusing filler fact, an icebreaker line, or a fact-of-the-moment prompt.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesUnique identifier for the fact
factYesThe useless fact text
sourceYesSource of the fact
permalinkYesPermanent link to the fact
source_urlYesURL to the source

Schema Changelog

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

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {}
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "fact": {
+      "description": "The useless fact text",
+      "type": "string"
+    },
+    "id": {
+      "description": "Unique identifier for the fact",
+      "type": "string"
+    },
+    "permalink": {
+      "description": "Permanent link to the fact",
+      "type": "string"
+    },
+    "source": {
+      "description": "Source of the fact",
+      "type": "string"
+    },
+    "source_url": {
+      "description": "URL to the source",
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "fact",
+    "source",
+    "source_url",
+    "permalink"
+  ],
+  "type": "object"
+}
  2. Changed2 schema fields changed
    • removedInput schema / examples
      Removed value: -[
-  {}
-]
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "fact": {
-      "description": "The useless fact text",
-      "type": "string"
-    },
-    "id": {
-      "description": "Unique identifier for the fact",
-      "type": "string"
-    },
-    "permalink": {
-      "description": "Permanent link to the fact",
-      "type": "string"
-    },
-    "source": {
-      "description": "Source of the fact",
-      "type": "string"
-    },
-    "source_url": {
-      "description": "URL to the source",
-      "type": "string"
-    }
-  },
-  "required": [
-    "id",
-    "fact",
-    "source",
-    "source_url",
-    "permalink"
-  ],
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "fact": {
+      "description": "The useless fact text",
+      "type": "string"
+    },
+    "id": {
+      "description": "Unique identifier for the fact",
+      "type": "string"
+    },
+    "permalink": {
+      "description": "Permanent link to the fact",
+      "type": "string"
+    },
+    "source": {
+      "description": "Source of the fact",
+      "type": "string"
+    },
+    "source_url": {
+      "description": "URL to the source",
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "fact",
+    "source",
+    "source_url",
+    "permalink"
+  ],
+  "type": "object"
+}
  4. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {}
+]
  5. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds useful behavioral context by naming the external API source and detailing the returned fields ('fact text with its id, the attributed source name, source URL, and a permalink'). It also specifies the language ('in English'). No contradictions found, and the description complements the annotations without over-explaining.

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 two sentences long, with the main action and source in the first sentence and return details and use cases in the second. Every word adds value, and the structure is clear and front-loaded. No fluff or redundancy.

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 zero-parameter tool with a rich output schema, the description covers purpose, source, return content, and intended use cases. The annotations cover safety (read-only, non-destructive, idempotent). There is no missing information needed to decide whether to invoke this tool. It is fully complete.

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?

The tool has zero parameters, so the input schema is complete and the description cannot add further parameter semantics. Per the rubric, a baseline of 4 applies when there are no parameters, as no additional explanation is needed. The description appropriately focuses on the output and use cases.

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's action: 'Return one random trivia fact in English from the Useless Facts API at uselessfacts.jsph.pl.' It specifies the resource (Useless Facts API), the verb (return), and the randomness (random trivia fact). This distinguishes it from sibling tools like today_fact, which likely returns a fact for a specific day.

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 provides clear use cases: 'Use it for an amusing filler fact, an icebreaker line, or a fact-of-the-moment prompt.' This gives context for when to invoke the tool, though it does not explicitly mention alternatives or when not to use it. That is acceptable for a simple, low-risk tool.

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

All uselessfacts 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

A4/5.0
Disambiguation4/5

Most tools have clearly distinct purposes (e.g., ask_pipeworx for general queries, ask_pipeworx_grounded for high-stakes verification, deep_research for multi-faceted research). However, some overlap exists among the ask_* variants and the prediction-market tools (bet_research vs. polymarket_edges vs. polymarket_arbitrage), which could cause misselection without careful reading of the detailed descriptions.

Naming Consistency4/5

Tool names consistently use snake_case and mostly follow the verb_noun pattern (e.g., list_subscriptions, resolve_entity, validate_claim). Minor deviations like random_fact and today_fact (adjective_noun) and pipeworx_feedback (noun_noun) introduce slight inconsistency, but the overall pattern is predictable.

Tool Count3/5

With 33 tools, the count exceeds the typical 3-15 range and even the 16-25 'heavy' threshold. While the server covers an unusually broad domain (data retrieval, prediction markets, memory, subscriptions, AI visibility), several tools could be consolidated (e.g., the six polymarket tools, trivial random_fact/today_fact). The scope partially justifies the count, but it feels over-provisioned.

Completeness4/5

The tool surface is remarkably comprehensive for a data platform: it covers querying, entity resolution, comparison, change feeds, memory persistence, subscription management, validation, and even meta-tool discovery. Minor gaps exist (e.g., no explicit update/delete for external data, but that is not the service's purpose). Overall, no obvious dead ends.

Resources