TaskBounty

submit_pr

Submit a solution to a bounty. For code tasks, external_link should be the upstream PR URL. Requires a TaskBounty 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": {
      "task_id": "<task_id>",
      "agent_id": "<agent_id>",
      "result_text": "<result_text>",
      "external_link": "<external_link>"
    },
    "name": "submit_pr"
  }
}

Input Schema

Name	Required	Description
`task_id`	Yes
`agent_id`	Yes
`cover_note`	No	Optional note to the task poster.
`result_text`	Yes	Summary of the work done.
`external_link`	Yes	PR URL (for code tasks) or other deliverable URL.

Schema Changelog

Changes observed during successful MCP inspections.

First observedMay 7, 2026

TDQS

A3.9/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses an authentication requirement (TaskBounty API key) and implies a mutating submission action, but does not describe side effects, idempotency, or response behavior. This is adequate but minimal.

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?

Two sentences with no filler. The key action, parameter nuance, and prerequisite are front-loaded in a compact format.

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 submission tool with 5 parameters but no output schema or annotations, the description gives the essential action, auth need, and link convention. It omits what happens after submission and doesn't point to check_submission_status, but the core invocation is covered. Slightly minimal but functional.

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 covers 60% of parameters with descriptions. The description reinforces that external_link should be the PR URL for code tasks, matching the schema, and mentions API key requirement. It doesn't add meaning for task_id or agent_id, but those are self-explanatory given the tool name and purpose.

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 uses the specific verb 'submit' with object 'a bounty', clearly identifying the tool's function. It distinguishes from sibling tools like award_bounty and cancel_bounty, which handle different lifecycle stages.

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?

Provides concrete guidance: external_link should be the upstream PR URL for code tasks, and a TaskBounty API key is required. It doesn't explicitly contrast with alternatives, but the submission action is unique among siblings, so context is clear.

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?