Skip to main content
Glama
Sign In

Koskamo

by com.koskamo
OverviewDiscussionsAdmin

Issue a new MCP owner key

koskamo_create_mcp_server_key
Destructive

For the owner of a listing: issue a fresh owner key, returned once, and stop the current one.

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_create_mcp_server_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe listing id returned at registration
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.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, but the description adds two things they cannot convey: the new key is returned only once, and issuing it terminates the current key. Those are exactly the consequences an agent must know before calling a destructive, non-idempotent operation.

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?

A single compact sentence with the audience/scope front-loaded and the two consequential facts — one-time return and invalidation of the old key — packed in without waste.

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 only two required parameters, full schema coverage, an output schema covering the returned key, and annotations carrying the safety profile, the description is close to sufficient. The only residual gap is whether the old key expires immediately or after a grace period, which an agent rotating keys would 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 coverage is 100% and both parameters carry their own descriptions (listing id, existing owner key, omitted from response), so the schema already does the heavy lifting. The description adds only the high-level hint that the caller must be the listing owner; it adds no syntax or format detail beyond the schema, so the baseline 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?

States a specific verb and resource (issue a fresh owner key) plus the acting scope ("for the owner of a listing"). The phrase "issue a fresh owner key ... and stop the current one" implicitly distinguishes it from the sibling koskamo_revoke_mcp_server_key, though it never names that sibling explicitly.

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

Usage Guidelines3/5

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

The description implies the situation (key rotation for an existing listing's owner) but gives no explicit when-to-use or when-not-to-use guidance and does not reference the revoke sibling it most closely competes with. An agent must infer that rotation rather than plain revocation is intended.

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