TaskBounty

compile_outcome_brief

Convert supplied scope into a reviewable diagnostic or execution brief. Returns missing questions and warnings. Does not infer facts, store data, publish work, authorize actions or spend money.

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": {
      "mode": "<mode>",
      "goal": "<goal>",
      "inputs": "<inputs>",
      "scope": "<scope>",
      "deliverables": "<deliverables>",
      "acceptance": "<acceptance>",
      "exclusions": "<exclusions>",
      "permissions": "<permissions>"
    },
    "name": "compile_outcome_brief"
  }
}

Input Schema

Name	Required	Description	Default
`goal`	Yes
`mode`	Yes
`scope`	Yes
`inputs`	Yes
`recipeId`	No
`acceptance`	Yes
`exclusions`	Yes
`permissions`	Yes
`deliverables`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 27, 2026

TDQS

C2.9/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that the tool returns missing questions and warnings and does not infer facts, store data, publish work, authorize actions, or spend money. However, it omits permission/auth requirements, rate limits, whether warnings block output, and fuller side-effect/persistence details.

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?

The description is three tightly structured sentences: purpose first, return behavior second, and safety boundaries third. There is no repetition or filler, and the key limitations are front-loaded enough for quick scanning.

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

Completeness2/5

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

This is a complex tool with many required parameters, no annotations, no output schema, and zero schema description coverage. The description covers purpose and some behavioral boundaries, but it is not complete enough for an agent to know required field semantics, mode selection, or what the returned brief actually contains.

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

Parameters1/5

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

The schema has 9 parameters, 8 required, with 0% description coverage. The description only alludes to scope and hints at mode through diagnostic/execution brief, but does not explain goal, inputs, deliverables, acceptance, exclusions, permissions, recipeId, formats, or constraints.

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 a specific verb and resource: convert supplied scope into a diagnostic or execution brief. It also clarifies that the result is reviewable and includes missing questions and warnings. It does not differentiate from siblings by name, but the function is clear and distinct enough in the sibling set.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The closest usage signal is the implied scenario of producing a reviewable brief, but there is no explicit when-to-use or when-not-to-use guidance. The description does not explain how to choose between diagnostic and execution modes or point to alternatives such as list_outcome_recipes.

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?