Skip to main content
Glama
meshive-mcp

meshive-mcp

Official
by meshive

Create Port Access Key

create_access_key

Creates an access key for a locked pod port so external programs can authenticate with a bearer token, requiring confirmation to issue the one-time secret.

Instructions

Create an access key for a locked port of a pod, only when the user asks for one. The key is a secret that lets a program outside the pod call the port: it is sent as Authorization: Bearer <key>, or as X-Meshive-Key: <key> when the app uses Authorization itself. With confirm=false (default) it only returns a summary and creates nothing; call again with confirm=true and the summary's pod_name after the user agreed. The confirmed answer has the 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. To call the app for your own work, use run_command inside the pod against http://localhost:, which needs no key. name is a label of 1-64 characters. expires_in_days is 30, 90 (default) or 365, or 0 for a key that never expires. The port must be locked (port_not_locked), and only a workspace admin or billing member can create keys. If a confirmed call times out or fails without a clear answer, don't call again: read access_keys first, because the key may exist, and a key whose value was lost can only be revoked. 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>",
      "name": "<name>"
    },
    "name": "create_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.
nameYes
portYesThe port number, from the pod's `endpoints` in the pods tool; it must be exposed over HTTPS (`access` locked or unlocked).
confirmNo
workspaceNo
operation_idNo
expires_in_daysNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.10.0

TDQS

A4.8/5.0
Behavior5/5

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

Goes far beyond the annotations: discloses that the key value is returned once and cannot be re-read, that the preview creates nothing, the exact auth header forms, the eligibility requirement (workspace admin or billing member), the port_not_locked precondition, and that the server keeps no operation record so operation_status cannot find it and a repeat runs again. The non-idempotent character is made concrete with recovery guidance.

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?

Purpose and the preview/confirm rule are front-loaded, and the operational details follow in a logical order. It is dense rather than wasteful, though the security handling guidance ('give it to the user... never use it yourself, never put it in files') restates the same constraint several ways and could be tightened.

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 mutation tool with a two-phase confirmation, this covers everything an agent needs: preconditions, permissions, the one-time secret handling, error recovery, and what the confirmed response contains. An output schema exists, yet the description still names the relevant fields (pod_name, access_key) in the context where they matter.

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?

With schema coverage at only 29%, the description carries the load and mostly does: `name` is 1-64 characters, `expires_in_days` accepts 30/90/365 or 0 for never, `port` must be an HTTPS-exposed port on the pod, and confirm semantics are spelled out. However, `workspace` and `operation_id` remain undocumented in both the schema and the description.

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 ('Create an access key for a locked port of a pod') and scopes it with an explicit trigger ('only when the user asks for one'). It is clearly distinguishable from access_keys, revoke_access_key and roll_access_key, and it explicitly routes self-use cases to run_command instead.

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 an explicit when-to-use rule, a two-phase protocol (confirm=false preview, then confirm=true after user agreement), and an explicit alternative for the agent's own calls (run_command against http://localhost:<port>, which needs no key). It also states the failure path: on an unclear confirmed result, read access_keys before retrying.

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