MentionForge

Get price and trial terms

get_pricing

Read-onlyIdempotent

Return MentionForge list price, trial policy, and CAIP-2 network for paying research_mentions ($0.02 USDC; 10 trial calls via X-Wallet or X-Sandbox-Key; always send Idempotency-Key). Use this free catalog when you need list price or trial terms — takes no arguments, never charges, never runs research, and needs no payment headers; for Worker liveness use health instead; for cited mentions use research_mentions.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`mcp`	Yes	Streamable HTTP MCP URL
`name`	Yes	Product name
`tool`	Yes	Paid MCP tool name (`research_mentions`)
`asset`	Yes	Asset symbol (USDC)
`trial`	Yes	How to consume the free trial
`eip712`	Yes	Permit domain extras
`pay_to`	Yes	Public payTo address for x402 exact (not a private key)
`network`	Yes	CAIP-2 network (eip155:8453 on production)
`endpoint`	Yes	REST POST /v1/research URL
`price_usdc`	Yes	List price in USDC (`0.02`)
`amount_atomic`	Yes	Atomic USDC amount (`20000` = $0.02)
`asset_address`	Yes	USDC contract on the advertised network
`payments_ready`	Yes	True when this origin can verify/settle x402
`free_trial_calls`	Yes	Trial calls per wallet (10)
`idempotency_header`	Yes	Send this header on every research call (`Idempotency-Key`)

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 21, 2026

addedInput schema / description

Added value: +"No arguments. Free price catalog."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "amount_atomic": {
+      "description": "Atomic USDC amount (`20000` = $0.02)",
+      "type": "string"
+    },
+    "asset": {
+      "description": "Asset symbol (USDC)",
+      "type": "string"
+    },
+    "asset_address": {
+      "description": "USDC contract on the advertised network",
+      "type": "string"
+    },
+    "eip712": {
+      "additionalProperties": false,
+      "description": "Permit domain extras",
+      "properties": {
+        "name": {
+          "description": "EIP-712 token name (USD Coin on Base mainnet)",
+          "type": "string"
+        },
+        "version": {
+          "description": "EIP-712 version",
+          "type": "string"
+        }
+      },
+      "required": [
+        "name",
+        "version"
+      ],
+      "type": "object"
+    },
+    "endpoint": {
+      "description": "REST POST /v1/research URL",
+      "type": "string"
+    },
+    "free_trial_calls": {
+      "description": "Trial calls per wallet (10)",
+      "type": "number"
+    },
+    "idempotency_header": {
+      "description": "Send this header on every research call (`Idempotency-Key`)",
+      "type": "string"
+    },
+    "mcp": {
+      "description": "Streamable HTTP MCP URL",
+      "type": "string"
+    },
+    "name": {
+      "description": "Product name",
+      "type": "string"
+    },
+    "network": {
+      "description": "CAIP-2 network (eip155:8453 on production)",
+      "type": "string"
+    },
+    "pay_to": {
+      "description": "Public payTo address for x402 exact (not a private key)",
+      "type": "string"
+    },
+    "payments_ready": {
+      "description": "True when this origin can verify/settle x402",
+      "type": "boolean"
+    },
+    "price_usdc": {
+      "description": "List price in USDC (`0.02`)",
+      "type": "string"
+    },
+    "tool": {
+      "description": "Paid MCP tool name (`research_mentions`)",
+      "type": "string"
+    },
+    "trial": {
+      "additionalProperties": false,
+      "description": "How to consume the free trial",
+      "properties": {
+        "header_sandbox": {
+          "description": "Header for operator sandbox key (`X-Sandbox-Key`)",
+          "type": "string"
+        },
+        "header_wallet": {
+          "description": "Header for trial EOA (`X-Wallet`)",
+          "type": "string"
+        }
+      },
+      "required": [
+        "header_wallet",
+        "header_sandbox"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "name",
+    "price_usdc",
+    "amount_atomic",
+    "asset",
+    "network",
+    "pay_to",
+    "asset_address",
+    "eip712",
+    "free_trial_calls",
+    "trial",
+    "endpoint",
+    "mcp",
+    "tool",
+    "payments_ready",
+    "idempotency_header"
+  ],
+  "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 declare readOnlyHint, openWorldHint=false, idempotentHint, and destructiveHint=false. The description adds tool-specific behavioral detail: it is a free catalog, never runs research, requires no payment headers, and notes the Idempotency-Key requirement for the related paid operation. This goes beyond the annotations without contradicting them.

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?

Two dense, purposeful sentences front-load the core return value and pricing details, then cover scope and sibling routing. Every clause earns its place; there is no filler or repetition.

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-argument, read-only catalog tool with an output schema, the description is complete. It covers purpose, cost and trial policy, network identifier, safety, missing prerequisites, and explicit sibling alternatives—nothing an agent needs to invoke it correctly is missing.

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 and the input schema already states 'No arguments.' The description reinforces this with 'takes no arguments' and 'free catalog,' but adds little beyond the schema. Given the 0-parameter baseline of 4, this is appropriate.

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 opens with a specific verb and resource: 'Return MentionForge list price, trial policy, and CAIP-2 network...' It also explicitly distinguishes itself from sibling tools by directing liveness checks to health and cited-mention work to research_mentions. There is no ambiguity about what get_pricing does.

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?

It states exactly when to use the tool ('when you need list price or trial terms') and when not to ('for Worker liveness use health instead; for cited mentions use research_mentions'). It also clarifies the absence of prerequisites: takes no arguments, never charges, runs no research, and needs no payment headers.

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.