Secret Store

Get environment

get_environment

Read-onlyIdempotent

Export every secret of an environment (or a subset of keys) as dotenv, JSON or shell exports. Requires secrets:read. Audited.

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": {
      "project": "<project>",
      "environment": "<environment>"
    },
    "name": "get_environment"
  }
}

Input Schema

Name	Required	Description	Default
`keys`	No	Only these keys (default: all)
`format`	No	Output format	dotenv
`project`	Yes	Project slug or id
`environment`	Yes	Environment slug or id, e.g. development, preview or production

Output Schema

Name	Required	Description
`keys`	Yes	Exactly the keys of `values`, in export order
`format`	Yes
`values`	Yes
`leftOut`	Yes
`project`	Yes
`environment`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent and non-destructive behavior, but the description adds genuinely new operational facts: the required 'secrets:read' scope and that the call is audited. It stops short of saying values are returned in plaintext or noting any rate limits or size constraints.

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?

Two short sentences with zero waste: capability and output formats first, then the authorization and audit facts. Front-loaded and easy to scan.

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 formatting need not be explained, and the description covers capability, formats, required scope and auditability. The only mild gap is that it does not warn that the response contains live secret values, which matters for an export tool.

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 description coverage is 100%, so the schema already documents project, environment, keys and format. The description only restates the keys subset and the format choices without adding syntax, defaults or project-vs-environment interaction detail. 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: 'Export every secret of an environment' with an optional subset of keys, plus the three output formats. An agent can distinguish this from a single-secret read or a secret listing. It does not name a sibling tool, so it falls short of a 5.

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?

Usage is implied by 'Export every secret ... as dotenv, JSON or shell exports', which tells the agent this is for bulk retrieval in a chosen format. There is no explicit when-to-use/when-not statement and no pointer to alternatives such as get_secret for a single value.

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

All Secret Store tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?