Younanix Memory MCP

query_lessons_premium

Premium Younanix Arete brief in an agent-native envelope (schema_version 2). Free for approved agents via x-agent-key. Otherwise requires inline x402 USDC payment ($0.10, Solana or Base) via x402-signature / x402-amount / x402-currency / x402-chain headers — without payment the tool returns a payment_required envelope carrying a pay_x402 next_action.

Input Schema

TableJSON Schema

Name	Required	Description
`query`	Yes	Natural language search query
`verbosity`	No	compact (default) trims lesson bodies and drops narrative prose; full returns everything.
`max_results`	No	Maximum number of results (default 10, max 25)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No
`error`	No
`status`	Yes
`surface`	Yes
`next_actions`	Yes
`schema_version`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedAug 21, 2026

addedInput schema / properties / verbosity

Added value: +{
+  "description": "compact (default) trims lesson bodies and drops narrative prose; full returns everything.",
+  "enum": [
+    "compact",
+    "full"
+  ],
+  "type": "string"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "data": {
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "error": {
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "next_actions": {
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "schema_version": {
+      "type": "number"
+    },
+    "status": {
+      "enum": [
+        "ok",
+        "insufficient",
+        "payment_required",
+        "rate_limited",
+        "error"
+      ],
+      "type": "string"
+    },
+    "surface": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "schema_version",
+    "surface",
+    "status",
+    "next_actions"
+  ],
+  "type": "object"
+}

AddedJun 28, 2026

TDQS

C2.9/5.0

Behavior4/5

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

With no annotations, the description carries the burden of behavior and does usefully disclose the x-agent-key free path, the x402 payment requirement including amount and chains, and the payment_required envelope with a pay_x402 action. It does not explicitly state that the operation is read-only or describe success-response shape, but the output schema covers the response.

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 packs payment, auth, and response behavior into a single dense sentence without fluff. The heavy punctuation and jargon reduce readability slightly, but every clause carries substantive integration information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The payment flow and authentication are well specified, and the output schema covers return structure. Missing context is the core purpose and differentiation from sibling query tools, which an agent needs to select and invoke the tool with confidence.

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%, so the schema fully documents query, verbosity, and max_results. The description adds no parameter-level meaning, which is acceptable at the baseline since the schema already supplies descriptions and enum constraints.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a noun phrase ('Premium Younanix Arete brief') rather than an explicit action like 'queries lessons' or 'returns a brief', leaving the core function to be inferred from the tool name and the 'query' parameter. It does not distinguish this tool from sibling tools query_lessons or query_lessons_full.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains payment and authentication mechanics but gives no guidance on when to choose this tool over query_lessons or query_lessons_full. There is no stated condition, prerequisite, or alternative comparison.

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

All Younanix Memory MCP 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.

Resources

Need Help?