Skip to main content
Glama

get_bounty_detail

Retrieve complete details of a specific bounty including description, evaluation criteria, repository URL, and reward.

Instructions

Fetch full details of a single bounty — description, evaluation criteria, repo URL, reward.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_id_or_slugYesThe task id (UUID) or human slug.

Implementation Reference

  • src/index.ts:79-116 (registration)
    Tool registration in the TOOLS array: defines name 'get_bounty_detail', description, and inputSchema requiring task_id_or_slug.
    const TOOLS = [
      {
        name: "list_open_bounties",
        description:
          "List currently open, funded bounties on TaskBounty. Returns title, reward, repo, language, and task id/slug.",
        inputSchema: {
          type: "object",
          properties: {
            platform: {
              type: "string",
              description: "Optional platform filter (e.g. 'github').",
            },
            language: {
              type: "string",
              description: "Optional language filter (e.g. 'typescript').",
            },
            limit: {
              type: "number",
              description: "Max items to return (default 25).",
            },
          },
        },
      },
      {
        name: "get_bounty_detail",
        description:
          "Fetch full details of a single bounty — description, evaluation criteria, repo URL, reward.",
        inputSchema: {
          type: "object",
          properties: {
            task_id_or_slug: {
              type: "string",
              description: "The task id (UUID) or human slug.",
            },
          },
          required: ["task_id_or_slug"],
        },
      },
  • Input schema for get_bounty_detail: accepts 'task_id_or_slug' (string, required).
    inputSchema: {
      type: "object",
      properties: {
        task_id_or_slug: {
          type: "string",
          description: "The task id (UUID) or human slug.",
        },
      },
      required: ["task_id_or_slug"],
    },
  • Handler for get_bounty_detail: validates task_id_or_slug, then calls tbFetch to GET /tasks/{encoded id}.
    case "get_bounty_detail": {
      const id = String(a.task_id_or_slug ?? "");
      if (!id) {
        return {
          content: [{ type: "text", text: "task_id_or_slug is required" }],
          isError: true,
        };
      }
      return await tbFetch(`/tasks/${encodeURIComponent(id)}`);
    }
  • tbFetch helper: makes HTTP requests to the TaskBounty API with auth, error handling, and returns ToolResult.
    async function tbFetch(
      path: string,
      init: RequestInit & { requireAuth?: boolean } = {},
    ): Promise<ToolResult> {
      const { requireAuth, headers, ...rest } = init;
      if (requireAuth && !API_KEY) {
        return {
          content: [
            {
              type: "text",
              text: "Missing TASKBOUNTY_API_KEY environment variable. Set it to your tb_live_* key from https://www.task-bounty.com/dashboard/api-keys.",
            },
          ],
          isError: true,
        };
      }
      const url = `${API_BASE}${path}`;
      const finalHeaders: Record<string, string> = {
        Accept: "application/json",
        ...(headers as Record<string, string> | undefined),
      };
      if (API_KEY) finalHeaders["Authorization"] = `Bearer ${API_KEY}`;
      if (rest.body && !finalHeaders["Content-Type"]) {
        finalHeaders["Content-Type"] = "application/json";
      }
    
      let res: Response;
      try {
        res = await fetch(url, { ...rest, headers: finalHeaders });
      } catch (err) {
        return {
          content: [
            {
              type: "text",
              text: `Network error calling ${url}: ${err instanceof Error ? err.message : String(err)}`,
            },
          ],
          isError: true,
        };
      }
    
      const text = await res.text();
      if (!res.ok) {
        return {
          content: [
            {
              type: "text",
              text: `HTTP ${res.status} ${res.statusText} from ${url}\n\n${text}`,
            },
          ],
          isError: true,
        };
      }
      return { content: [{ type: "text", text }] };
    }
Behavior2/5

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

No annotations provided, so description carries full burden. It only states what is fetched but does not disclose any behavioral traits (e.g., read-only, idempotent, no side effects, authentication requirements). For a simple retrieval, minimal transparency is acceptable but not fully disclosed.

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?

Description is a single sentence, front-loaded with purpose. It is concise, though could potentially include a brief note on return format or additional fields. No waste.

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?

Given the simple nature (single param, no output schema), the description covers the basic purpose and output fields. It is fairly complete but could mention it is a read-only operation to align with behavioral transparency.

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 coverage is 100% (one parameter with description). The description adds no extra meaning beyond what the schema provides. Baseline 3 is appropriate as schema already documents the parameter.

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 clearly states the verb 'Fetch' and resource 'full details of a single bounty', listing specific fields (description, criteria, repo URL, reward). It is distinct from sibling tools which either list, submit, or modify bounties.

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?

No explicit guidance on when to use this vs alternatives. While the purpose is clear, it does not mention when to choose this over get_bounty_submissions or list_open_bounties. Implicit from name but no direct guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/eliottreich/taskbounty-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server