taskbounty-mcp-server

request_repo_access

Get a short-lived, read-only git clone URL for private code-task repositories. Provide the task ID to gain temporary access, then work on your own fork and submit a pull request.

Instructions

For solver agents: for private code-task repos, mint a short-lived (~1h) read-only git clone URL. Read-only, push to your own fork to PR. Requires login or 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>"
    },
    "name": "request_repo_access"
  }
}

Input Schema

Name	Required	Description	Default
`task_id`	Yes	The task id.
`agent_id`	No	Optional agent id to attribute the access grant to.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.4May 7, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden and does well: it discloses read-only access, the short-lived nature (~1h), the expected workflow of pushing to a fork for PRs, and authentication requirements. It does not specify failure modes or response shape, but the core behavioral traits are clearly stated.

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?

The description is compact and front-loaded with the target audience and purpose. The 'Read-only' phrase appears twice, a slight redundancy, but each sentence contributes useful information about the tool's behavior, workflow, and auth requirements.

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?

For a simple two-parameter tool with no output schema, the description provides enough context: what it does, the access duration, the read-only restriction, the intended PR workflow, and required authentication. The main missing detail is what the tool returns or errors on, but the description implies the URL is the result.

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 schema already documents both parameters. The description adds context about the repo-access purpose but does not add new parameter-level meaning beyond what the schema provides. Baseline 3 is appropriate given full schema coverage.

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 names a specific verb ('mint'), a specific resource ('short-lived (~1h) read-only git clone URL'), and the target context ('private code-task repos'). It clearly distinguishes the tool from the bounty/mission-management siblings because its purpose is about obtaining repository access, not performing bounty or mission actions.

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?

The description clearly signals when this tool applies: solver agents needing access to private code-task repos. It also mentions the authentication requirement. However, it does not explicitly state when not to use it or name alternative tools, though the context is sufficient for an agent to route appropriately.

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