taskbounty-mcp-server

post_from_current_file

Create a bounty for the file currently open in your editor, enabling repo owners to incentivize fixes directly from their coding environment.

Instructions

For repo owners: (coming soon) post a bounty from the file currently open in your editor. Not yet implemented.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "post_from_current_file"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.7.0Aug 26, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It explicitly and honestly states that the tool is not implemented, which is the most important behavioral fact an agent needs. It does not speculate about what happens if the tool is invoked, but for a placeholder tool this is sufficient.

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 one short, front-loaded sentence that communicates audience, intended action, and availability status efficiently. There is minor redundancy between 'coming soon' and 'not yet implemented', but it does not significantly hurt conciseness.

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 tool with no parameters, no output schema, and no annotations, the description is largely complete: it tells the agent what the tool is for, who it is for, and that it is not yet usable. It could optionally point to a sibling alternative, but that is not essential here.

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?

The input schema has no parameters and schema description coverage is 100%, so there is nothing the description needs to add about parameters. The baseline of 4 applies.

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 states the intended action clearly: post a bounty from the file currently open in the editor, and identifies the target audience (repo owners). This differentiates it from sibling tools like post_from_issue by the resource it operates on. However, the message that it is 'coming soon' and 'not yet implemented' means the tool does not currently perform its stated purpose.

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?

The 'Not yet implemented' note gives a clear signal that the tool should not be used yet. It does not, however, provide guidance about when it will be available or suggest an alternative tool to use instead, so usage context is incomplete.

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