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

NameRequiredDescriptionDefault
queryNoInput for the paid endpoint: not needed.

Output 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.
ready_requestNoExact paid HTTP request (method, url with your input, optional json_body) to send with an x402 client.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / ready_request
      Added value: +{
+  "description": "Exact paid HTTP request (method, url with your input, optional json_body) to send with an x402 client."
+}
  2. Changed1 schema field changed
    • addedOutput schema / properties / free_teaser
      Added value: +{
+  "description": "Free sample output of this SKU (truncated); null if unavailable."
+}
  3. 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."
  4. 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"
+}
  5. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare safety traits (readOnly, idempotent, non-destructive); the description goes well beyond them by disclosing the delivery model: a free sample plus paid URL and pay steps, with no charge at call time and a $17 Base USDC x402 charge for the full result. That payment/return behavior is exactly what the annotations cannot convey.

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 tight sentences, each earning its place: artifact, usage routing, then pricing/return behavior, front-loaded in that order. No repetition of the title or redundant restatement.

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-required-param download tool with an output schema present, the description supplies everything else the agent needs: audience, exclusion, cost, and what the response contains. Nothing material is missing.

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' parameter is already documented as 'not needed' in the schema, so the description carries no additional parameter detail. Baseline 3 applies since the schema does the heavy lifting and no enum/format nuance is missing.

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 and artifact: 'Download an English PDF playbook with 7 side-income plays starting under $100.' It also differentiates itself from the JSON/automation siblings and implicitly from nebenverdienst-pdf, so an agent can tell what it produces without opening the schema.

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 when-to-use ('Use when a human wants a full guide') and when-not ('Not for agent automation (use the JSON tools)'), routing the caller to an alternative tool class. Nothing about selection is left to inference.

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
Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources