Skip to main content
Glama

report_outcome

Report solution success or failure to improve ranking in Hivemind MCP's debugging knowledge base.

Instructions

Report whether a solution worked or not. Helps improve solution rankings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
solution_idNoThe ID of the solution from search results.
outcomeYesDid the solution work?

Implementation Reference

  • The core implementation of the report_outcome tool. Sends HTTP POST to Hivemind backend (/report) with optional solution_id and required outcome (success/failure), returns confirmation.
    export async function reportOutcome(
      solutionId: number | undefined,
      outcome: "success" | "failure"
    ): Promise<OutcomeResult> {
      const response = await fetch(`${API_BASE}/report`, {
        method: "POST",
        headers: {
          "Content-Type": "application/json",
        },
        body: JSON.stringify({ solution_id: solutionId, outcome }),
      });
    
      if (!response.ok) {
        throw new Error(`Report failed: ${response.statusText}`);
      }
    
      return response.json();
    }
  • MCP tool schema defining input parameters: optional solution_id (number), required outcome (success|failure). Used in ListTools response.
    {
      name: "report_outcome",
      description:
        "Report whether a solution worked or not. Helps improve solution rankings.",
      inputSchema: {
        type: "object",
        properties: {
          solution_id: {
            type: "number",
            description: "The ID of the solution from search results.",
          },
          outcome: {
            type: "string",
            enum: ["success", "failure"],
            description: "Did the solution work?",
          },
        },
        required: ["outcome"],
      },
    },
  • src/index.ts:366-374 (registration)
    MCP server registration: handles CallToolRequest for report_outcome by extracting args and invoking reportOutcome handler, returning JSON stringified result.
    case "report_outcome": {
      const result = await reportOutcome(
        args?.solution_id as number | undefined,
        args?.outcome as "success" | "failure"
      );
      return {
        content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
      };
    }
  • TypeScript interface defining the expected return type from the reportOutcome API call.
    interface OutcomeResult {
      success: boolean;
      message: string;
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states the tool reports outcomes to improve rankings, implying a write/mutation operation, but doesn't disclose behavioral traits such as permissions required, whether the action is reversible, rate limits, or what happens after reporting (e.g., confirmation). For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 highly concise and front-loaded: two sentences with zero waste. The first sentence states the purpose, and the second adds context ('Helps improve solution rankings'). Every sentence earns its place, making it efficient and easy to parse.

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?

Given the tool's complexity (mutation with 2 parameters, no annotations, no output schema), the description is incomplete. It lacks details on behavioral aspects (e.g., what 'improve solution rankings' entails, confirmation of action), and while the schema covers parameters, the overall context for proper usage is insufficient. A mutation tool should provide more guidance on effects and requirements.

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%, with clear descriptions for both parameters (solution_id and outcome with enum). The description adds no additional meaning beyond the schema, such as explaining how solution_id is obtained or the impact of reporting outcomes. Baseline 3 is appropriate since the schema does the heavy lifting, but no extra value is provided.

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 clearly states the tool's purpose: 'Report whether a solution worked or not' specifies the verb (report) and resource (solution outcome). It distinguishes from siblings like search_kb or get_skill by focusing on feedback rather than retrieval. However, it doesn't explicitly differentiate from contribute_solution, which might also involve solution-related actions.

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 description provides minimal guidance: 'Helps improve solution rankings' implies usage for ranking purposes, but it doesn't specify when to use this tool versus alternatives like contribute_solution or update_project_entry, nor does it mention prerequisites (e.g., needing a solution_id from search results). No explicit when/when-not or alternative tools are named.

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/Kevthetech143/hivemind-mcp'

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