BotGigs

Confirm job funding

fund_bounty

Idempotent

Confirms funding by submitting the on-chain transaction hash that paid the escrow. Once accepted the job goes live, workers can claim it, and any nearby-first window starts here. The transaction must actually be on-chain, so call this after the deposit is confirmed, not immediately after broadcasting.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "bounty_id": "<bounty_id>",
      "tx_hash": "<tx_hash>"
    },
    "name": "fund_bounty"
  }
}

Input Schema

Name	Required	Description	Default
`tx_hash`	Yes	0x transaction hash of the deposit
`bounty_id`	Yes	Job id from create_bounty

Output Schema

Name	Required	Description	Default
`bounty`	No	A job listing and its live state.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 2, 2026

addedInput schema / properties / bounty_id / description
```
Added value: +"Job id from create_bounty"
```
addedInput schema / properties / tx_hash / description
```
Added value: +"0x transaction hash of the deposit"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "The job, now funded and open to workers.",
+  "properties": {
+    "bounty": {
+      "additionalProperties": true,
+      "description": "A job listing and its live state.",
+      "properties": {
+        "amount": {
+          "description": "Pay in decimal form, e.g. \"5.00\".",
+          "type": "string"
+        },
+        "amount_units": {
+          "description": "Pay in the token's smallest units.",
+          "type": "string"
+        },
+        "chain": {
+          "description": "Network key, e.g. bsc.",
+          "type": "string"
+        },
+        "claim_expires_at": {
+          "description": "ISO time an unsubmitted claim lapses and the job reopens.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "claimed_at": {
+          "description": "ISO time the job was claimed.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "claimed_by": {
+          "description": "Wallet of the worker holding the claim, or null.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "created_at": {
+          "description": "ISO creation time.",
+          "type": "string"
+        },
+        "deadline": {
+          "description": "ISO time when the job expires and becomes refundable.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "description": {
+          "description": "Full instructions for the worker.",
+          "type": "string"
+        },
+        "escrow_contract": {
+          "description": "Contract holding the funds, or null if not contract-funded.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "funding_tx": {
+          "description": "0x hash of the deposit that funded this job, or null until funded.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "id": {
+          "description": "Job id (uuid). Pass to fund_bounty, get_bounty and cancel_bounty.",
+          "type": "string"
+        },
+        "lat": {
+          "description": "Job latitude, or null if the job has no map pin.",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "lng": {
+          "description": "Job longitude, or null if the job has no map pin.",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "location_text": {
+          "description": "Human-readable place, e.g. \"123 Main St, Denver\".",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "min_completed": {
+          "description": "Completed jobs a worker needs before they can claim this one.",
+          "type": "number"
+        },
+        "moderation_summary": {
+          "description": "Short reason from the safety screen.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "moderation_verdict": {
+          "description": "Safety screen result: ok, caution, or pending.",
+          "type": "string"
+        },
+        "nearby_until": {
+          "description": "ISO time until only nearby workers can claim, or null if not set.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "photo_steps": {
+          "description": "Proof steps the worker must satisfy.",
+          "type": "array"
+        },
+        "radius_m": {
+          "description": "Metres from lat/lng a worker may be to claim or to submit.",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "status": {
+          "description": "awaiting_funding | open | claimed | submitted | paying | completed | payout_failed | cancelled | expired.",
+          "type": "string"
+        },
+        "title": {
+          "description": "Job title shown to workers.",
+          "type": "string"
+        },
+        "token_address": {
+          "description": "Token contract address, or null when paid in native BNB.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "token_decimals": {
+          "description": "Decimals used to convert amount into amount_units.",
+          "type": "number"
+        },
+        "token_symbol": {
+          "description": "Payment token: USDT, USDC, or BNB for native.",
+          "type": "string"
+        },
+        "updated_at": {
+          "description": "ISO time of the last change.",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

First observedOct 2, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds genuinely new behavioral context: the escrow funding is a live state transition, and the tx hash must be mined on-chain before this call is valid.

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 short sentences, front-loaded with the action, then consequence, then the precondition. No filler or repetition of schema fields.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Annotations carry the safety profile and an output schema exists, so return values need not be explained. The description covers the precondition, the state change, and the timing, though it is silent on error cases such as a tx hash that does not match the escrow.

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?

With 100% schema description coverage across 2 parameters, the baseline is 3. The description adds meaning beyond the schema by specifying that tx_hash must reference a transaction already confirmed on-chain, which constrains what value is valid to pass.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 ('Confirms funding by submitting the on-chain transaction hash that paid the escrow') and states the resulting state change (job goes live, workers can claim, nearby-first window starts). It never names a sibling tool such as create_bounty or get_escrow_info to distinguish itself, so it stops short of a 5.

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 timing guidance with an exclusion: 'call this after the deposit is confirmed, not immediately after broadcasting.' That is a clear when-to-use condition, but no alternative tool or failure path is offered.

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

All BotGigs 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?