Skip to main content
Glama

Reveal stored values

reveal_values
Read-onlyIdempotent

The tool that returns secret values, whole environments, file contents and saved passwords (get_project shows sensitive field values only to secrets:read); call it only when the task needs the values in your context, and never repeat them in chat, logs or files the user did not ask for. To put an environment into a .env file use pull_env instead, which keeps the values away from you. item secret: the value of one key in one environment (to call an API, say). item environment: every readable value of one environment, or only keys, as dotenv, JSON or shell exports, followed by a note naming keys left out (protected, sealed or outside this token's limits); billed as a pull. item file: one secure file's contents, UTF-8 text or base64, up to 1 MB; attachments and larger files open only in the web app. item login: one saved login's URL, username, password and notes. Find names first with list_project_items. Protected items need an approved request_access grant, and no tool can read a sealed one. One client approval of this tool covers every item kind, so a client that asks per tool asks once. Read-only, audited with the names read. Requires secrets:read (secret, environment), files:read and full access to the project (file), or logins:read (login).

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": {
      "item": "<item>",
      "project": "<project>"
    },
    "name": "reveal_values"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNosecret only
fileNofile only: file id, or its exact name as list_project_items item files shows it
itemYesWhat to reveal
keysNoenvironment only: only these keys, up to 200 (default: every key the token may read)
loginNologin only: login id, or its exact name as list_project_items item logins shows it
formatNoenvironment only: dotenv (KEY=value lines, default), json (one object) or shell (export lines)
projectYesProject slug or id
environmentNosecret, environment: required

Output Schema

NameRequiredDescriptionDefault
keyNo
urlNo
keysNoExactly the keys of `values`, in export order
nameNo
notesNo
valueNo
formatNo
valuesNo
contentNo
leftOutNo
projectNo
encodingNoText files come back as utf-8, binaries as base64
passwordNo
usernameNo
contentTypeNo
environmentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses audit logging with the names read, per-item-kind permission scopes, that environment reveals are billed as a pull, a 1 MB file ceiling with web-app-only fallback, and that sealed items are unreadable by any tool. It also notes one client approval covers all item kinds, which is non-obvious invocation context.

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?

The most important constraint (call only when values are needed in context, never echo them) is front-loaded, and the per-item-kind breakdown is scannable. It is dense and semicolon-heavy, packing permissions and limits into a long trailing clause, but almost no sentence is redundant.

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 8-parameter, multi-mode read tool with an output schema, the description covers the gaps that matter: authorization per item kind, size and item limits, protected/sealed edge cases, billing, and where to find names. Return-value shape is correctly left to the output schema.

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 baseline is 3; the description adds meaning by tying each parameter to an item kind ('item secret: the value of one key in one environment', 'item environment: every readable value ... or only keys'), clarifying the relationship between item, keys, format, and the selector fields. It stops short of restating every constraint the schema already carries, which is appropriate.

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?

The opening sentence names a specific verb and resource (returns secret values, environments, file contents, saved passwords) and then enumerates each item kind with its precise scope. It explicitly distinguishes itself from get_project and pull_env, so an agent can separate it from siblings without opening a schema.

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?

It states when to call ('only when the task needs the values in your context'), when not to (never repeat values in chat, logs, or files), and names concrete alternatives: pull_env for writing a .env file, list_project_items to find names first, request_access for protected items. Exclusions and routing are both explicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources