Skip to main content
Glama

geld machen x402 agent utilities

by dev.fly.geld-machen-x402
OverviewDiscussionsAdmin

Side Income with Under $100: 7 Practical Plays

side-income-pdf
Read-onlyIdempotent

Download an English PDF playbook with 7 side-income plays starting under $100. Use when a human wants a full guide. Not for agent automation (use the JSON tools). Returns a free sample plus the paid URL and pay steps (no charge here); the full result costs $17 Base USDC via x402.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoInput for the paid endpoint: not needed.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
skuYes
noteNo
payToNo
priceNo
methodNo
networkNo
paid_urlYes
how_to_payYes
teaser_urlNo
your_inputNo
free_teaserNoFree sample output of this SKU (truncated); null if unavailable.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / free_teaser
      Added value: +{
+  "description": "Free sample output of this SKU (truncated); null if unavailable."
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Optional input (e.g. url / address / text) to pass to the paid endpoint as ?q= or JSON body."New value: +"Input for the paid endpoint: not needed."
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "how_to_pay": {
+      "type": "string"
+    },
+    "method": {
+      "type": "string"
+    },
+    "network": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "note": {
+      "type": "string"
+    },
+    "paid_url": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "payTo": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "price": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "sku": {
+      "type": "string"
+    },
+    "teaser_url": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "your_input": {}
+  },
+  "required": [
+    "sku",
+    "paid_url",
+    "how_to_pay"
+  ],
+  "type": "object"
+}
  4. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations, which only cover the safety profile. It discloses the payment model (free sample returned here, full result costs $17 Base USDC via x402, no charge on this call) and what the response contains, which is the critical behavioral fact for a paywalled resource.

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?

Three sentences, zero filler, front-loaded with the artifact and then the routing and payment facts in priority order. Every sentence earns its place.

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?

Complete for a zero-required-param download tool. Even though an output schema exists, the description still pre-empts the paywall confusion by explaining the free-sample-plus-paid-URL return shape, so an agent will not misread a successful call as a delivered guide.

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% and the single 'query' param is explicitly marked 'not needed', so the schema carries the meaning. The description adds no parameter-level detail beyond that, which is the expected baseline when the schema does the work.

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 (Download), the artifact (an English PDF playbook), and its content (7 side-income plays under $100). The 'English' qualifier implicitly separates it from the German sibling nebenverdienst-pdf, and 'use the JSON tools' separates it from the analysis siblings.

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 gives the trigger ('Use when a human wants a full guide') and the exclusion ('Not for agent automation'), plus a redirection to the JSON tool family. An agent can route correctly without opening the schema.

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

All geld machen x402 agent utilities toolsInspect
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