Skip to main content
Glama
Sign In

Koskamo

by com.koskamo
OverviewDiscussionsAdmin

Hide or relist your MCP listing

koskamo_update_mcp_server_visibility
Destructive

For the owner of a listing: hidden true unlists a published listing; hidden false re-runs the live check and publishes an owner-hidden or check-hidden listing when it passes.

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": {
      "id": "<id>",
      "owner_key": "<owner_key>",
      "hidden": "<hidden>"
    },
    "name": "koskamo_update_mcp_server_visibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe listing id returned at registration
hiddenYestrue unlists the listing; false relists it after a passing live check
reasonNoOptional reason shown with a hidden listing in the admin console
owner_keyYesThe owner key issued when the listing was published; verified for this listing and omitted from the response

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already disclose destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the safety profile is known. The description usefully adds that relisting re-runs a live check and only publishes on pass, plus the owner-hidden/check-hidden state names, but leaves unresolved what happens on a failed check and why the operation is not idempotent. With annotations carrying much of the burden, this is a modest but real value-add.

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?

A single well-structured sentence with the owner scoping front-loaded and the two branches of hidden laid out in parallel. It is dense but not padded; the hyphenated state names (owner-hidden, check-hidden) are the only mildly opaque element.

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?

With full schema coverage, an output schema, and rich annotations, the description only needs to supply the workflow logic, and it does so for the visibility toggle. It stops short of explaining the failure path of the live check or how owner_key verification errors surface, which an owner mutating state might want to know.

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%, so every parameter including id, owner_key, and reason is already documented in the schema. The description restates the hidden flag's meaning without adding format, validation, or failure detail beyond what the schema provides, so the baseline of 3 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 gives a specific action pair tied to the resource: hidden=true unlists a published listing, hidden=false relists it. The audience ("For the owner of a listing") and the listing-scoped nature separate it well from the sibling koskamo_update_mcp_server, though no sibling is named explicitly.

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?

It clearly states the condition that selects each branch of the hidden flag, including the precondition that relisting requires a passing live check. It does not cover when not to use this tool (e.g., when a general update via koskamo_update_mcp_server is more appropriate) or what to do if the live check fails.

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

All Koskamo toolsInspect
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