Mundane

make_offer

Offer a task to a worker. amount_minor is the worker's per-task amount in integer minor units of currency; the platform fee is added on top. expires_in_seconds is the pending-offer lifetime in seconds. On success, the all-in total is held in escrow. Structured errors report budget, worker eligibility / ask-rate, wallet, or spend-cap failures.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`message`	No	Optional note sent to the worker with the offer.
`task_id`	Yes	The task being offered, as returned by post_task.
`currency`	No	ISO-4217 currency code. USD is the only currency supported today.	USD
`worker_id`	Yes	The worker to offer it to, as returned by search_workers.
`amount_minor`	Yes	What the worker is paid, integer minor units. Mundane's fee is added on top, so you are charged more than this.
`idempotency_key`	No	Optional key of your own choosing so a retry does not create a second offer or hold escrow twice.
`expires_in_seconds`	No	How long the worker has to accept before the offer lapses. Default is 24 hours.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`status`	No
`offer_id`	No
`expires_at`	No
`escrow_hold_id`	No
`platform_fee_minor`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedSep 22, 2026

addedInput schema / properties / amount_minor / description

Added value: +"What the worker is paid, integer minor units. Mundane's fee is added on top, so you are charged more than this."

addedInput schema / properties / currency / description

Added value: +"ISO-4217 currency code. USD is the only currency supported today."

addedInput schema / properties / expires_in_seconds / description

Added value: +"How long the worker has to accept before the offer lapses. Default is 24 hours."

addedInput schema / properties / idempotency_key / description

Added value: +"Optional key of your own choosing so a retry does not create a second offer or hold escrow twice."

addedInput schema / properties / message / description

Added value: +"Optional note sent to the worker with the offer."

addedInput schema / properties / task_id / description

Added value: +"The task being offered, as returned by post_task."

addedInput schema / properties / worker_id / description

Added value: +"The worker to offer it to, as returned by search_workers."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "escrow_hold_id": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Escrow Hold Id"
+    },
+    "expires_at": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Expires At"
+    },
+    "offer_id": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Offer Id"
+    },
+    "platform_fee_minor": {
+      "anyOf": [
+        {
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Platform Fee Minor"
+    },
+    "status": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Status"
+    }
+  },
+  "title": "OfferOut",
+  "type": "object"
+}

First observedSep 22, 2026

TDQS

A4.3/5.0

Behavior5/5

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

The description discloses the consequential side-effects: the platform fee is added to amount_minor, the all-in total is held in escrow on success, and structured errors cover budget, worker eligibility/ask-rate, wallet, or spend-cap failures. This goes well beyond the sparse annotation hints and tells an agent what to expect externally.

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 with no filler. The purpose is front-loaded, and the parameter explanations are compact and woven into the behavioral context. 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?

With a full schema, annotations, output schema present, and a description that covers side-effects and failure modes, an agent has everything needed to select and invoke this tool correctly. The only minor gap is explicit usage routing, but it is not essential.

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?

The input schema already covers all parameters with descriptions, so the baseline is 3. The description restates the key semantics for amount_minor and expires_in_seconds, but it does not add information that is not already present in the schema.

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?

Description opens with 'Offer a task to a worker' – a specific verb and resource that clearly distinguishes this from sibling tools like post_task and search_workers. It is immediately obvious what action this tool performs without needing to inspect 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 Guidelines3/5

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

Usage is implied: this is the step after a task exists and a worker is selectedaiman. The schema hints at prerequisites by saying task_id comes from post_task and worker_id from search_workers, but the description itself does not explicitly say when to use this tool or when to prefer a sibling.

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

All Mundane 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.