Skip to main content
Glama
meshive-mcp

meshive-mcp

Official
by meshive

Roll Port Access Key

roll_access_key

Replaces an access key's value while keeping its name and port, issues a new id, and supports an overlap window for moving clients to the new value.

Instructions

Replace the value of one access key, only when the user asks: the key keeps its name and port and gets a new value and a new id. Use it when a value may have leaked, before a key expires, or to replace a key that has expired (expired in access_keys): its old value is dead already, so overlap_seconds is ignored and there is no overlap. The old value keeps working for overlap_seconds, so the user's programs can be moved to the new value: 3600 (1 hour, default), 86400 (24 hours), 604800 (7 days), or 0 to stop the old value at once. The new value expires after the same lifetime the key was created with, counted from now. With confirm=false (default) it only returns a summary and changes nothing; call again with confirm=true and the summary's pod_name after the user agreed. The confirmed answer has the new value in access_key, this once: it can't be read again. Give it to the user who asked and nothing else. Never use it yourself, and never put it in files, commits, commands or other tools. The port must be locked, and only a workspace admin or billing member can roll keys. If a confirmed call times out or fails without a clear answer, don't call again: read access_keys first. The server keeps no operation record of this call, so operation_status can't look it up and a repeated confirmed call runs again.

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": {
      "pod": "<pod>",
      "port": "<port>",
      "key_id": "<key_id>"
    },
    "name": "roll_access_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
podYesThe pod_name from the pods tool. Its display name also works, except on a confirmed call (confirm=true) that opens a port, changes a key or signs out browsers: use the `pod_name` the preview returned.
portYesThe port number, from the pod's `endpoints` in the pods tool; it must be exposed over HTTPS (`access` locked or unlocked).
key_idYesThe key's `id` from the access_keys tool.
confirmNo
workspaceNo
operation_idNo
overlap_secondsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.10.0

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond the annotations: overlap_seconds actually leaves the old value alive, the new value inherits the original lifetime counted from now, overlap is ignored for expired keys, confirm=false is a no-op preview, and the new value is returned exactly once and unreadable afterward. It also discloses authorization requirements (port locked, admin or billing member), the absence of any operation record so operation_status cannot find it, and that a repeated confirmed call runs again — fully consistent with idempotentHint=false and destructiveHint=false.

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?

Front-loaded with the purpose, then organized into behavior, confirmation flow, security handling, and failure recovery — no filler sentences. It is dense and fairly long, but every paragraph carries operational or safety information that is not available elsewhere in the definition.

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?

Covers what an agent needs for a non-idempotent, security-sensitive mutation: preconditions, dry-run workflow, overlap semantics, one-time secret handling, permissions, and retry-safety after an ambiguous failure. An output schema exists, and the description still flags the key return fields, so nothing critical is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 43%, and the description compensates heavily: it enumerates the meaningful overlap_seconds values with durations, explains the 0 case, states that overlap is ignored for expired keys, and defines confirm's preview-versus-execute semantics including using the preview's pod_name. Only workspace and operation_id are left unexplained, which is a minor residual gap against a 7-parameter tool.

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 precise verb and resource ('Replace the value of one access key') and immediately adds the scope constraint that the key keeps its name and port but gets a new value and new id. That distinguishes it cleanly from create_access_key and revoke_access_key without needing their schemas.

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

Usage Guidelines5/5

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

Gives explicit triggers (leaked value, pre-expiry, or replacing an already-expired key) and a hard precondition ('only when the user asks'). It also routes the agent through the correct alternative flow: preview with confirm=false, then re-call with confirm=true after user agreement, and points to access_keys for recovery after an ambiguous failure.

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