Skip to main content
Glama
network-terminal-mcp

network-terminal-mcp

by evgenyzh

terminal_write_secret

Send a secret into a persistent terminal session from exactly one source: value, env var, or file; prefer env/file to keep plaintext out of client history.

Instructions

Send a secret from exactly one source: value, env, or file.

Prefer env or file; plaintext value remains in client history. The server redacts known secrets and never returns or audits the secret value.

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": {
      "session_id": "<session_id>"
    },
    "name": "terminal_write_secret"
  }
}

Input Schema

NameRequiredDescriptionDefault
envNo
fileNo
valueNo
session_idYes

Output Schema

NameRequiredDescriptionDefault
okYes
stateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.5.0
    • removedOutput schema / description
      Removed value: -"Result of writing a secret; the value is never included."
    • removedOutput schema / properties / bytes_sent
      Removed value: -{
      -  "title": "Bytes Sent",
      -  "type": "integer"
      -}
    • addedOutput schema / properties / ok
      Added value: +{
      +  "title": "Ok",
      +  "type": "boolean"
      +}
    • removedOutput schema / properties / session_id
      Removed value: -{
      -  "title": "Session Id",
      -  "type": "string"
      -}
    • removedOutput schema / properties / source
      Removed value: -{
      -  "enum": [
      -    "value",
      -    "env",
      -    "file"
      -  ],
      -  "title": "Source",
      -  "type": "string"
      -}
    • changedOutput schema / required
      Previous value: -[
      -  "session_id",
      -  "source",
      -  "bytes_sent",
      -  "state"
      -]New value: +[
      +  "ok"
      +]
    • changedOutput schema / title
      Previous value: -"TerminalSecretResult"New value: +"WriteReply"
  2. Changed10 schema fields changedv0.2.1
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / entry
      Removed value: -{
      -  "title": "Entry",
      -  "type": "string"
      -}
    • addedInput schema / properties / env
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Env"
      +}
    • addedInput schema / properties / file
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "File"
      +}
    • addedInput schema / properties / value
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Value"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "session_id",
      -  "entry"
      -]New value: +[
      +  "session_id"
      +]
    • changedOutput schema / description
      Previous value: -"Result of writing a pass-referenced secret; never contains the secret."New value: +"Result of writing a secret; the value is never included."
    • removedOutput schema / properties / entry
      Removed value: -{
      -  "title": "Entry",
      -  "type": "string"
      -}
    • addedOutput schema / properties / source
      Added value: +{
      +  "enum": [
      +    "value",
      +    "env",
      +    "file"
      +  ],
      +  "title": "Source",
      +  "type": "string"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "session_id",
      -  "entry",
      -  "bytes_sent",
      -  "state"
      -]New value: +[
      +  "session_id",
      +  "source",
      +  "bytes_sent",
      +  "state"
      +]
  3. First observedv0.1.1

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the exactly-one-source constraint, warns that plaintext values persist in client history, and states that the server redacts known secrets and never returns or audits them. It omits what happens if multiple sources are supplied simultaneously and what permissions are required.

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?

Three short sentences, front-loaded with the core constraint and then the safety caveats. No filler and no repetition of schema fields.

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?

An output schema exists, so return-value explanation is unnecessary, and the description still adds that the secret is never returned or audited. The main residual gap is error behavior for conflicting sources and the meaning of the required session_id.

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 0%, so the description must compensate; it clarifies that value/env/file are mutually exclusive alternatives and flags the risk of 'value'. It does not clarify whether 'env' is an environment-variable name or a literal value, or whether 'file' is a path, and session_id is never mentioned.

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 names a specific action and resource ('Send a secret') and enumerates the three accepted input sources, so an agent immediately knows what the tool does. It never explicitly contrasts itself with the sibling 'terminal_write', leaving the differentiation to be inferred from the tool name.

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?

'Prefer env or file; plaintext value remains in client history' gives clear guidance on which input source to choose, which is real usage advice. However, it never says when to use this tool rather than plain terminal_write, nor any prerequisite about an open session.

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