Koskamo

Update an MCP server listing

koskamo_update_mcp_server

Destructive

Edit a listing you registered, using the owner key issued when it was published. Send id, owner_key and only the fields to change. With a verified proof the edit publishes at once. Changing endpoint, auth or docsUrl, or sending tools (even unchanged names), refreshes live schemas first; a failed or incomplete catalog check refuses the edit. An endpoint moved outside the ownership proof is queued for review. The id is fixed, visibility cannot change, and the response omits the key. Same path and limits as PATCH /api/v1/mcp-directory/servers/{id}; no durable receipt.

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>"
    },
    "name": "koskamo_update_mcp_server"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	The listing id returned at registration
`auth`	No	How callers sign in; a change re-runs the live check
`name`	No	Product name
`note`	No	Optional note for reviewers when the edit is queued
`tools`	No	Sending tool names refreshes live schemas even when names are unchanged; replaced by the observed list after a complete check
`docsUrl`	No	Your documentation page for this server; a change re-runs the live check
`category`	No	Directory category
`endpoint`	No	Streamable HTTP endpoint (https); a change re-runs the live check
`operator`	No	Company that runs the server
`useCases`	No	1-6 use cases from your documentation
`owner_key`	Yes	The owner key issued when the listing was published; verified for this listing and omitted from the response
`companyUrl`	No	Https company website; an empty string clears it
`description`	No	20-600 characters, factual
`requirements`	No	Up to 4 prerequisites a user must already have (e.g. a vendor account or paid subscription), beyond endpoint sign-in

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 8, 2026

changedInput schema / properties / tools / description

Previous value: -"Replaced by the live tool list when the check passes"New value: +"Sending tool names refreshes live schemas even when names are unchanged; replaced by the observed list after a complete check"

AddedNov 4, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Goes well beyond the annotations: explains that a verified proof publishes immediately, that endpoint/auth/docsUrl/tools changes trigger a live schema refresh, that a failed or incomplete catalog check refuses the edit, that an endpoint moved outside the ownership proof is queued for review, that the response omits the key, and that there is no durable receipt. These side effects are exactly what an agent needs to predict consequences for a destructiveHint=true mutation.

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?

Five compact sentences, each carrying distinct information: auth mechanism, patch instruction, publish behavior, refresh/refusal rules, queue behavior, then invariants and endpoint equivalence. Nothing is repeated from the schema and there is no filler.

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 14-parameter mutation with an output schema and annotations, the description covers credentials, partial-update semantics, refusal and review paths, and omitted response fields. Nothing an agent needs in order to invoke it correctly is 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 coverage is already 100%, so the schema carries the per-field burden. The description still adds real meaning: it instructs sending only the fields to change (patch semantics, not full replacement) and warns that sending 'tools' refreshes live schemas even when names are unchanged.

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?

Opens with a specific verb and resource: 'Edit a listing you registered, using the owner key issued when it was published.' It also carves out boundaries against siblings in the same family, notably that 'the id is fixed, visibility cannot change', which separates it from the visibility-update tool and the registration tool.

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?

Gives clear when-to-use framing (you must own the listing and hold the owner key) and implicit when-not guidance (visibility cannot change, id is fixed, so those edits need another tool). It does not name the alternative sibling tool explicitly, which keeps it short of a 5.

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

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