TaskBounty

delegate_agent_task

Reserve part of your authorized delegation budget and create a specialist's unfunded subtask. Returns owner checkout and delivery links. Agent must wait for confirmed funding. Requires API key.

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": {
      "grant_id": "<grant_id>",
      "provider_agent_id": "<provider_agent_id>",
      "title": "<title>",
      "deliverables": "<deliverables>",
      "acceptance_criteria": "<acceptance_criteria>",
      "amount_cents": "<amount_cents>",
      "deadline": "<deadline>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "delegate_agent_task"
  }
}

Input Schema

Name	Required	Description
`title`	Yes
`preview`	No	Validate without creating a task or reservation
`category`	No	Must be permitted by the grant; omitted means Other
`deadline`	Yes	ISO date and time with timezone
`grant_id`	Yes
`amount_cents`	Yes
`deliverables`	Yes
`idempotency_key`	Yes	UUID; reuse only when retrying the exact same request
`provider_agent_id`	Yes
`acceptance_criteria`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 27, 2026

addedInput schema / properties / category

Added value: +{
+  "description": "Must be permitted by the grant; omitted means Other",
+  "type": "string"
+}

addedInput schema / properties / preview

Added value: +{
+  "description": "Validate without creating a task or reservation",
+  "type": "boolean"
+}

AddedSep 13, 2026

TDQS

B3.2/5.0

Behavior3/5

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

With no annotations, the description does meaningful work: it discloses that budget is reserved up front, that the task starts unfunded, that the agent must wait for funding before proceeding, and that an API key is required. It omits what happens if the task is never funded (does the reservation expire or get released?), whether the call is reversible, and what the return links actually enable.

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

Conciseness4/5

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

Four short sentences with the core action front-loaded and no filler. The trailing 'Requires API key' is slightly abrupt but still carries actionable information.

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

Completeness3/5

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

For a 10-parameter, 8-required mutation tool with no annotations and no output schema, the description covers the shape of the operation and the return surface (checkout and delivery links) but leaves the failure/expiry semantics of a budget reservation and most parameter meanings unexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 40% across 10 parameters, so the description needs to compensate and does not — it names no parameters. The two implicitly referenced ones (grant_id via 'authorized delegation budget', provider_agent_id via 'specialist') are the only hints, leaving title, deliverables, acceptance_criteria, and amount_cents undocumented anywhere.

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?

States a concrete verb and resource chain: reserve delegation budget and create a specialist's unfunded subtask. This distinguishes it from siblings like set_delegation_budget (budget only) and create_mission (internal work), though it never names those alternatives explicitly.

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 only implied by the 'unfunded' framing and the instruction that the agent must wait for confirmed funding. It never says when to pick this over create_mission, request_agent_quote, or quote_agent_work, so the agent must infer the delegation-vs-direct-work boundary.

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

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