MentionForge

Get price and trial terms

get_pricing

Read-onlyIdempotent

Get list price, trial policy, and CAIP-2 network for MentionForge paid research tools. Use this free catalog to check costs or trial terms before making paid calls.

Instructions

Return MentionForge list price, trial policy, and CAIP-2 network for the paid research tools. Omit include_catalog or set it true to keep tools[] and endpoints[]; set false to drop those arrays and keep settlement fields only; extra keys are rejected; {} is valid. Use this free catalog when you need list price or trial terms. For Worker liveness use get_health instead. For cited mentions use research_mentions. Never charges and never runs research; needs no payment headers. Paid tools cost $0.02 USDC and share 10 trial calls via X-Wallet or X-Sandbox-Key. those paid tools (not this catalog) must always send Idempotency-Key.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`include_catalog`	No	Optional boolean. Default true.

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)
`tools`	No	Catalog of MCP tools. Paid tools share one 10-call trial. Omitted when include_catalog is false.
`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
`endpoints`	No	REST surfaces. Paid POST routes verify against /v1/research x402 requirements. Omitted when include_catalog is false.
`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.

Changed4 schema fields changedv1.2.2Sep 21, 2026

removedInput schema / description

Removed value: -"No arguments. Free price catalog."

addedInput schema / properties / include_catalog

Added value: +{
+  "description": "Optional boolean. Default true.",
+  "type": "boolean"
+}

addedOutput schema / properties / endpoints

Added value: +{
+  "description": "REST surfaces. Paid POST routes verify against /v1/research x402 requirements. Omitted when include_catalog is false.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "kind": {
+        "description": "free never charges; paid shares the $0.02 resource",
+        "enum": [
+          "free",
+          "paid"
+        ],
+        "type": "string"
+      },
+      "method": {
+        "description": "HTTP method",
+        "type": "string"
+      },
+      "path": {
+        "description": "REST path",
+        "type": "string"
+      }
+    },
+    "required": [
+      "method",
+      "path",
+      "kind"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / tools

Added value: +{
+  "description": "Catalog of MCP tools. Paid tools share one 10-call trial. Omitted when include_catalog is false.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "kind": {
+        "description": "free never charges; paid shares the 10-call trial",
+        "enum": [
+          "free",
+          "paid"
+        ],
+        "type": "string"
+      },
+      "name": {
+        "description": "MCP tool name",
+        "type": "string"
+      },
+      "price_usdc": {
+        "description": "List price when paid (`0.02`)",
+        "type": "string"
+      }
+    },
+    "required": [
+      "name",
+      "kind"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

First observedv1.0.0Sep 21, 2026

TDQS

A4.6/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 valuable behavioral context beyond annotations: 'Never charges and never runs research; needs no payment headers.' It also discloses that paid tools require Idempotency-Key, which is useful context for the broader workflow. It doesn't contradict annotations.

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 dense but efficient, with the core purpose front-loaded in the first sentence. Every sentence adds information: parameter behavior, usage routing, cost/authentication context, and sibling distinctions. It is slightly long but each clause earns its place, and the structure is logical.

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 read-only catalog tool with one optional parameter and an output schema, the description is complete. It covers purpose, parameter behavior, usage routing, cost implications, authentication requirements, and validation rules. The output schema handles return-value documentation, so the description doesn't need to explain that.

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?

Schema coverage is 100% for the single parameter, so the schema already documents include_catalog. The description adds meaning beyond the schema by explaining the behavioral effect of the parameter: 'Omit include_catalog or set it true to keep tools[] and endpoints[]; set false to drop those arrays and keep settlement fields only.' It also notes 'extra keys are rejected; {} is valid,' which is useful validation context not in the schema.

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 for the paid research tools.' This clearly distinguishes the tool from siblings like get_health and research_mentions, which are explicitly named as alternatives. The purpose is unambiguous and immediately actionable.

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?

The description provides explicit when-to-use guidance: 'Use this free catalog when you need list price or trial terms.' It also names alternatives with their conditions: 'For Worker liveness use get_health instead. For cited mentions use research_mentions.' This is exactly the kind of routing an agent needs.

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

Deploy Server