Skip to main content
Glama

Report whether an MCP server worked

koskamo_report_mcp_outcome
Destructive

After using an MCP server listed on Koskamo, say whether it worked for your task: success, partial or failure, optionally for one tool. Only daily counts per listing and tool are kept (no text, IP or client), one signal per caller per listing per hour. Returns the listing's 30-day totals.

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": {
      "server_id": "<server_id>",
      "outcome": "<outcome>"
    },
    "name": "koskamo_report_mcp_outcome"
  }
}

Input Schema

NameRequiredDescriptionDefault
outcomeYessuccess, partial or failure
server_idYesDirectory listing id of the server you used
tool_nameNoExact name of the tool you called; omit for the server as a whole

Output Schema

NameRequiredDescriptionDefault
noteNo
toolsYes
totalYes
failureYes
partialYes
successYes
server_idYes
window_daysYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Adds substantial context beyond annotations: data retention limited to daily counts per listing and tool with no text, IP or client, plus a rate limit of one signal per caller per listing per hour. This is strong disclosure, though it does not reconcile the write with the destructiveHint=true annotation or explain what the 30-day totals look like beyond their existence.

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?

Front-loads the action and allowed outcomes, then packs retention and rate-limit constraints into a short clause without waste. Every sentence carries information an agent needs before calling.

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

Completeness5/5

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

For a three-parameter write tool with full schema coverage, an output schema and rich annotations, the description covers when to call, privacy posture, rate limits and return summary. Nothing essential is left missing.

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?

Schema description coverage is already 100%, so baseline is 3; the description adds modest value by restating the outcome enum and clarifying that the tool dimension is optional ('optionally for one tool'). It does not explain server_id format expectations beyond the schema.

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?

States a specific verb and resource: report whether an MCP server worked, with the allowed outcomes (success, partial, failure) and optional per-tool granularity. The 'After using an MCP server listed on Koskamo' framing separates it from siblings like koskamo_report_mcp_issue, which is about problems rather than outcome signal.

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?

Makes the trigger condition explicit ('after using an MCP server listed on Koskamo') and scopes the optional tool-level signal with 'optionally for one tool.' It does not name alternatives or say when not to use it (e.g., use koskamo_report_mcp_issue for defects), so it stops short of full routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources