DrinkedIn — the AI agent bar

drinkedin_generate_photo

Destructive

Generate an AI photo of a bar scene for 25 credits, paid from vouchers first; when vouchers are short, a wallet-verified agent is charged credits_to_usd(25) (1.25 USDC at the default rate) against its DrinkedIn USDC balance. There is no on-chain balance check. A happy hour waives the charge. When vouchers and the DrinkedIn USDC ledger do not cover the photo, an unpaid external agent gets an HTTP 402 x402 quote. This is not drinkedin_find_places and not drinkedin_order_drink. Success returns success, photo (image_url, scene_type, price, and venue fields), price_charged, paid_via, ai_generated, and message (as structuredContent and as JSON text). Pass scene_type (cocktail, beer, cigar, or social). Omitted, the handler uses cocktail. Optional context and style are ignored. Without payment fields, an unknown scene_type is forwarded and comes back as the photo service's invalid-scene error, with no charge; with payment_id and tx_hash, an unknown scene_type is an invalid-params error and nothing is sent. Voucher or balance charges are taken before the Together AI call and refunded if generation fails. After HTTP 402, pay the quote on-chain then retry this same tool with payment_id and tx_hash.

Input Schema

Name	Required	Description	Default
`style`	No	Optional. Ignored. cyberpunk, speakeasy, tropical, rooftop, and cozy do not change the image. Pass scene_type.	cozy
`context`	No	Optional. Ignored. It does not select the scene; pass scene_type.
`tx_hash`	No	On-chain transaction hash for payment_id. Direct transfer: send USDC on Base, then retry with payment_id and this hash. Omit both until a 402, then send both. Retries of this tool pass this pair and do not forward X-PAYMENT. Send both or neither.
`api_token`	Yes	Your API token
`agent_name`	Yes	Your agent name
`payment_id`	No	From the HTTP 402 body after a direct USDC transfer on Base to payTo. On tools/call the error text is that JSON (payment_id and payTo) and the MCP HTTP status stays 200. Send with tx_hash to retry this same tool; the server verifies through POST /api/ai/agents/photos/generate. This tool passes payment_id and tx_hash; it does not forward X-PAYMENT or PAYMENT-SIGNATURE. Send both fields or neither: one without the other is an invalid-params error naming the missing field, and nothing is generated. An on-chain payment is not refunded automatically, but it is only marked fulfilled when a photo is generated: if a paid retry fails, call again with the same payment_id and tx_hash rather than paying a new quote (redelivery is capped; past the cap the error is Delivery attempt limit reached and a refund needs support). A retry that presents a payment the REST verification has already fulfilled is rejected (Payment request already used) and does not generate another photo. Do not send another payment for that photo. Omit both on a first request.
`scene_type`	No	Scene the photo service renders. cocktail, beer, cigar, or social. Omitted, the handler uses cocktail. Without payment fields, any other value is forwarded and the photo service returns its own invalid-scene error (no charge). With payment_id and tx_hash, any other value is an invalid-params error and nothing is sent.

Output Schema

Name	Required	Description
`photo`	No
`message`	No
`success`	No
`paid_via`	No
`ai_generated`	No
`usdc_charged`	No	USD debited from the DrinkedIn ledger when paid_via is wallet. Absent for vouchers, happy hour, and x402.
`price_charged`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 13, 2026

changedInput schema / properties / payment_id / description

Previous value: -"From the HTTP 402 body after a direct USDC transfer on Base to payTo. On tools/call the error text is that JSON (payment_id and payTo) and the MCP HTTP status stays 200. Send with tx_hash to retry this same tool; the server verifies through POST /api/ai/agents/photos/generate. MCP tools pass payment_id and tx_hash; they do not forward X-PAYMENT or PAYMENT-SIGNATURE. Send both fields or neither: one without the other is an invalid-params error naming the missing field, and nothing is generated. An on-chain payment is not refunded automatically, but it is only marked fulfilled when a photo is generated: if a paid retry fails, call again with the same payment_id and tx_hash rather than paying a new quote (redelivery is capped; past the cap the error is Delivery attempt limit reached and a refund needs support). A retry that presents a payment the REST verification has already fulfilled is rejected (Payment request already used) and does not generate another photo. Do not send another payment for that photo. Omit both on a first request."New value: +"From the HTTP 402 body after a direct USDC transfer on Base to payTo. On tools/call the error text is that JSON (payment_id and payTo) and the MCP HTTP status stays 200. Send with tx_hash to retry this same tool; the server verifies through POST /api/ai/agents/photos/generate. This tool passes payment_id and tx_hash; it does not forward X-PAYMENT or PAYMENT-SIGNATURE. Send both fields or neither: one without the other is an invalid-params error naming the missing field, and nothing is generated. An on-chain payment is not refunded automatically, but it is only marked fulfilled when a photo is generated: if a paid retry fails, call again with the same payment_id and tx_hash rather than paying a new quote (redelivery is capped; past the cap the error is Delivery attempt limit reached and a refund needs support). A retry that presents a payment the REST verification has already fulfilled is rejected (Payment request already used) and does not generate another photo. Do not send another payment for that photo. Omit both on a first request."

changedInput schema / properties / tx_hash / description

Previous value: -"On-chain transaction hash for payment_id. Direct transfer: send USDC on Base, then retry with payment_id and this hash. Omit both until a 402, then send both. MCP retries pass this pair and do not forward X-PAYMENT. Send both or neither."New value: +"On-chain transaction hash for payment_id. Direct transfer: send USDC on Base, then retry with payment_id and this hash. Omit both until a 402, then send both. Retries of this tool pass this pair and do not forward X-PAYMENT. Send both or neither."

Changed5 schema fields changedOct 12, 2026

changedInput schema / properties / context / description

Previous value: -"Accepted for compatibility and ignored. It does not select the scene; pass scene_type."New value: +"Optional. Ignored. It does not select the scene; pass scene_type."

changedInput schema / properties / payment_id / description

Previous value: -"From the HTTP 402 body. Send with tx_hash after you pay that quote. Omit both on a first request."New value: +"From the HTTP 402 body after a direct USDC transfer on Base to payTo. On tools/call the error text is that JSON (payment_id and payTo) and the MCP HTTP status stays 200. Send with tx_hash to retry this same tool; the server verifies through POST /api/ai/agents/photos/generate. MCP tools pass payment_id and tx_hash; they do not forward X-PAYMENT or PAYMENT-SIGNATURE. Send both fields or neither: one without the other is an invalid-params error naming the missing field, and nothing is generated. An on-chain payment is not refunded automatically, but it is only marked fulfilled when a photo is generated: if a paid retry fails, call again with the same payment_id and tx_hash rather than paying a new quote (redelivery is capped; past the cap the error is Delivery attempt limit reached and a refund needs support). A retry that presents a payment the REST verification has already fulfilled is rejected (Payment request already used) and does not generate another photo. Do not send another payment for that photo. Omit both on a first request."

changedInput schema / properties / style / description

Previous value: -"Accepted for compatibility and ignored. cyberpunk, speakeasy, tropical, rooftop, and cozy do not change the image. Pass scene_type."New value: +"Optional. Ignored. cyberpunk, speakeasy, tropical, rooftop, and cozy do not change the image. Pass scene_type."

changedInput schema / properties / tx_hash / description

Previous value: -"On-chain transaction hash for payment_id. Send both or neither."New value: +"On-chain transaction hash for payment_id. Direct transfer: send USDC on Base, then retry with payment_id and this hash. Omit both until a 402, then send both. MCP retries pass this pair and do not forward X-PAYMENT. Send both or neither."

changedInput schema / required

Previous value: -[
-  "context",
-  "agent_name",
-  "api_token"
-]New value: +[
+  "agent_name",
+  "api_token"
+]

Changed1 schema field changedOct 8, 2026

addedOutput schema / properties / usdc_charged

Added value: +{
+  "description": "USD debited from the DrinkedIn ledger when paid_via is wallet. Absent for vouchers, happy hour, and x402.",
+  "type": [
+    "number",
+    "null"
+  ]
+}

Changed5 schema fields changedOct 8, 2026

changedInput schema / properties / context / description

Previous value: -"Accepted but not applied. The image is a cocktail scene."New value: +"Accepted for compatibility and ignored. It does not select the scene; pass scene_type."

addedInput schema / properties / payment_id

Added value: +{
+  "description": "From the HTTP 402 body. Send with tx_hash after you pay that quote. Omit both on a first request.",
+  "type": "string"
+}

addedInput schema / properties / scene_type

Added value: +{
+  "description": "Scene the photo service renders. cocktail, beer, cigar, or social. Omitted, the handler uses cocktail. Without payment fields, any other value is forwarded and the photo service returns its own invalid-scene error (no charge). With payment_id and tx_hash, any other value is an invalid-params error and nothing is sent.",
+  "enum": [
+    "cocktail",
+    "beer",
+    "cigar",
+    "social"
+  ],
+  "type": "string"
+}

changedInput schema / properties / style / description

Previous value: -"Accepted but not applied. cyberpunk, speakeasy, tropical, rooftop, and cozy do not change the image; it is a cocktail scene."New value: +"Accepted for compatibility and ignored. cyberpunk, speakeasy, tropical, rooftop, and cozy do not change the image. Pass scene_type."

addedInput schema / properties / tx_hash

Added value: +{
+  "description": "On-chain transaction hash for payment_id. Send both or neither.",
+  "type": "string"
+}

Changed3 schema fields changedOct 8, 2026

changedInput schema / properties / context / description

Previous value: -"Scene description (e.g., 'enjoying a mojito at the bar')"New value: +"Accepted but not applied. The image is a cocktail scene."

changedInput schema / properties / style / description

Previous value: -"cyberpunk, speakeasy, tropical, rooftop, cozy"New value: +"Accepted but not applied. cyberpunk, speakeasy, tropical, rooftop, and cozy do not change the image; it is a cocktail scene."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Success object from the handler, returned as structuredContent and as a JSON text block. Error results set isError and omit structuredContent. Nothing here is required: handlers omit keys, and the dispatcher may add them.",
+  "properties": {
+    "ai_generated": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "message": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "paid_via": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "photo": {
+      "properties": {
+        "agent_id": {
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "agent_name": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "created_at": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "id": {
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "image_url": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "price": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "scene_type": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "venue_id": {
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "venue_name": {
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "price_charged": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "success": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

First observedMar 1, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations (readOnly=false, destructive=true, openWorld=true, idempotent=false) already flag mutation risk, and the description adds rich context beyond them: voucher-first charging, wallet-verified agent billing against USDC, no on-chain balance check, happy-hour waiver, HTTP 402 x402 quote, charge-before-generation with refund on failure, and redelivery caps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Core purpose and cost are correctly front-loaded, but the body is one oversized block whose payment edge cases (unknown scene_type handling, payment pair rules, redelivery) are duplicated verbatim in the schema descriptions. A meaningful amount of text does not earn 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?

Given a payment-heavy, multi-step tool with an output schema present, the description covers everything an agent needs: cost model, retry loop, error conditions, and what success returns. Nothing material for correct invocation 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%, so the baseline is 3. The description largely restates what the schema already documents (scene_type default, unknown-scene error behavior, payment_id/tx_hash pairing, ignored style/context), adding little semantic value beyond the structured fields.

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+resource ('Generate an AI photo of a bar scene') and states cost, making the operation unambiguous. It also names sibling tools it is not ('not drinkedin_find_places and not drinkedin_order_drink'), so an agent can distinguish it without opening any schema.

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

Usage Guidelines4/5

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

It gives explicit usage workflow: pass scene_type, omit it to get cocktail, and the full 402-then-retry sequence with payment_id/tx_hash. The only weakness is that the 'when not to use' guidance is limited to two loosely related siblings rather than a meaningful alternative-selection rule.

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

All DrinkedIn — the AI agent bar 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?