MentionForge

Check Worker liveness

health

Read-onlyIdempotent

Check MentionForge Worker liveness and whether paid research can settle. Use this free pulse when you only need uptime — takes no arguments, never charges, and needs no X-Wallet, Idempotency-Key, or PAYMENT-SIGNATURE; for list price or trial terms use get_pricing instead; for cited mentions use research_mentions.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`status`	Yes	`ok` when the MCP factory ran
`payments_ready`	Yes	True when paid research_mentions can settle on this origin
`source_backends`	Yes	Non-secret adapter modes. Native Reddit/X are optional operator upgrades.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 21, 2026

addedInput schema / description

Added value: +"No arguments. Free liveness pulse."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "payments_ready": {
+      "description": "True when paid research_mentions can settle on this origin",
+      "type": "boolean"
+    },
+    "source_backends": {
+      "additionalProperties": false,
+      "description": "Non-secret adapter modes. Native Reddit/X are optional operator upgrades.",
+      "properties": {
+        "news": {
+          "description": "news adapter mode",
+          "type": "string"
+        },
+        "reddit": {
+          "description": "reddit adapter mode: public or oauth",
+          "type": "string"
+        },
+        "reviews": {
+          "description": "reviews adapter mode",
+          "type": "string"
+        },
+        "web": {
+          "description": "web adapter mode: wiki or brave+wiki",
+          "type": "string"
+        },
+        "x": {
+          "description": "x adapter mode: web or api",
+          "type": "string"
+        }
+      },
+      "required": [
+        "reddit",
+        "x",
+        "web",
+        "news",
+        "reviews"
+      ],
+      "type": "object"
+    },
+    "status": {
+      "description": "`ok` when the MCP factory ran",
+      "type": "string"
+    }
+  },
+  "required": [
+    "status",
+    "payments_ready",
+    "source_backends"
+  ],
+  "type": "object"
+}

First observedSep 20, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already provide readOnlyHint=true, idempotentHint=true, destructiveHint=false, but the description adds valuable behavioral context beyond that: it is free, takes no arguments, and requires no X-Wallet, Idempotency-Key, or PAYMENT-SIGNATURE. These are authentication and cost traits not covered by annotations, raising transparency significantly.

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 a single, dense sentence that front-loads the primary purpose, then packs usage conditions, free/auth traits, and sibling routing. Every clause earns its place; no filler 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?

Given a zero-parameter tool with a rich output schema and annotations covering safety and idempotency, the description covers everything an agent needs: what it checks, when to use it, costs, auth requirements, and alternatives. The output schema exists, so return-value documentation is unnecessary.

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?

With zero parameters, the baseline is 4. The schema already says 'No arguments' and coverage is 100%. The description reinforces this by saying 'takes no arguments,' which is consistent and adds a small reminder, but there is no parameter-level meaning to add since none exist.

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?

States a specific verb and resource: 'Check MentionForge Worker liveness and whether paid research can settle.' It also differentiates from siblings by explicitly routing list-price/trial queries to get_pricing and cited-mention queries to research_mentions, so an agent can select it without opening schemas.

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?

Explicitly says when to use: 'Use this free pulse when you only need uptime.' It also names the alternatives and their conditions: 'for list price or trial terms use get_pricing instead; for cited mentions use research_mentions.' No ambiguity about context.

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

All MentionForge tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.