Agoreum (read only, no account)

Checks Agoreum sells, with prices and how to call them

list_agoreum_tools

Read-onlyIdempotent

List the services Agoreum runs itself: prompt-injection screening, MCP server, x402 endpoint, ERC-8004 agent and USDC payment checks, and payment-backed feedback. Each comes with its marketplace price, its direct x402 price and URL, an example input and its input schema. Direct calls need no Agoreum account. Use it when an agent needs one of these checks before it reads, pays or trusts something; search_services finds what other providers sell. Read-only. Settlement is on Base, a live network. The USDC here is real money and transfers are irreversible.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`tools`	Yes
`network`	Yes
`how_to_buy`	Yes
`seller_name`	Yes
`seller_slug`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "how_to_buy": {
+      "type": "string"
+    },
+    "network": {
+      "title": "Network",
+      "type": "string"
+    },
+    "seller_name": {
+      "title": "Seller Name",
+      "type": "string"
+    },
+    "seller_slug": {
+      "title": "Seller Slug",
+      "type": "string"
+    },
+    "tools": {
+      "items": {
+        "description": "One service Agoreum sells itself, with both ways to buy it.",
+        "properties": {
+          "direct_price_usdc": {
+            "pattern": "^(?!^[-+.]*$)[+-]?0*\\d*\\.?\\d*$",
+            "title": "Direct Price Usdc",
+            "type": "string"
+          },
+          "direct_url": {
+            "title": "Direct Url",
+            "type": "string"
+          },
+          "example_input": {
+            "additionalProperties": true,
+            "title": "Example Input",
+            "type": "object"
+          },
+          "input_schema": {
+            "additionalProperties": true,
+            "title": "Input Schema",
+            "type": "object"
+          },
+          "marketplace_path": {
+            "title": "Marketplace Path",
+            "type": "string"
+          },
+          "marketplace_price_usdc": {
+            "pattern": "^(?!^[-+.]*$)[+-]?0*\\d*\\.?\\d*$",
+            "title": "Marketplace Price Usdc",
+            "type": "string"
+          },
+          "slug": {
+            "title": "Slug",
+            "type": "string"
+          },
+          "summary": {
+            "title": "Summary",
+            "type": "string"
+          },
+          "tags": {
+            "items": {
+              "type": "string"
+            },
+            "title": "Tags",
+            "type": "array"
+          },
+          "title": {
+            "title": "Title",
+            "type": "string"
+          }
+        },
+        "required": [
+          "slug",
+          "title",
+          "summary",
+          "tags",
+          "marketplace_price_usdc",
+          "direct_price_usdc",
+          "direct_url",
+          "marketplace_path",
+          "example_input",
+          "input_schema"
+        ],
+        "title": "AgoreumTool",
+        "type": "object"
+      },
+      "title": "Tools",
+      "type": "array"
+    }
+  },
+  "required": [
+    "how_to_buy",
+    "network",
+    "seller_name",
+    "seller_slug",
+    "tools"
+  ],
+  "title": "AgoreumTools",
+  "type": "object"
+}

First observedOct 19, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations it adds decision-relevant context: direct calls need no account, settlement runs on Base as a live network, and USDC transfers are real and irreversible. The irreversibility warning materially changes how an agent should handle downstream paid calls.

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?

Front-loaded with the resource, then the per-item contents, then the usage rule and the payment caveat. The service enumeration is dense but each item is load-bearing; the only mild redundancy is restating the tool's scope after already naming the services.

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?

An output schema exists, so return values need not be spelled out, yet the description still previews the entry contents. For a zero-parameter listing tool with rich annotations, nothing an agent needs before calling 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?

Zero parameters, so the baseline is 4. The description correctly implies a no-argument call and explains the shape of what comes back (prices, URLs, example input, schema), though it cannot add parameter meaning where none exists.

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 names a specific verb and resource — listing the services Agoreum runs itself — and enumerates them (prompt-injection screening, MCP server, x402 endpoint, ERC-8004 agent, USDC payment checks, feedback). It also states what each entry carries (marketplace price, x402 price/URL, example input, schema), which no sibling tool 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?

Explicit trigger: 'Use it when an agent needs one of these checks before it reads, pays or trusts something.' It also names the alternative and draws the boundary — 'search_services finds what other providers sell' — versus Agoreum's own services listed here.

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

All Agoreum (read only, no account) 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?