Runcrate

List secret names

list_secrets

Read-onlyIdempotent

List the names of the variables a machine launched in the environment gets, and where each comes from, never a value: key, sensitive, updated_at, source and active. source is "runcrate" for a secret set in Runcrate, or the environment's secret manager ("doppler:/", "infisical:/", "1password:"), whose names are those of its last read; active is false when a Runcrate secret of the same name overrides a manager's. A manager's names carry source_status (ok, failing, not_checked) and, when failing, source_error: while it fails, every launch in the environment is refused with "Secret manager unreachable". Every instance and job launched in the environment gets these as environment variables, so a command can read $HF_TOKEN without the value ever passing through you. Values set for one launch (run_job variables, a schedule spec's env or env_vars) win over all of them. Secrets are added, changed and removed only in the Runcrate dashboard (https://runcrate.ai/dashboard/settings/secrets) by a workspace owner or admin. A secret manager (Doppler, Infisical or 1Password) is connected once at https://runcrate.ai/dashboard/settings/integrations and linked to an environment on the Secrets page; no agent can connect or link one. When a command needs a secret that is not listed, ask the user to add it there, or to link their secret manager (they will need a Doppler service token, an Infisical machine identity, or a 1Password service account; the page walks them through it); never ask them to paste a value to you. When a source is failing, tell the user its source_error and to check it at the integrations page.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_secrets"
  }
}

Input Schema

Name	Required	Description	Default
`workspace`	No	Workspace ID (optional: defaults to the authenticated workspace)
`environment`	No	Environment name (optional: defaults to the environment this session acts in)

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 21, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the read-only annotations, the description discloses critical behavior: values are never returned, manager sources may be ok/failing/not_checked, failing managers block launches with a specific error, and Runcrate secrets override manager secrets of the same name. It also clarifies precedence rules for launch-specific values and the limits of agent-side secret management.

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 core purpose is front-loaded and nearly every sentence carries operational value, but the opening sentence is dense and the description is long overall. It is appropriately complete for a tool with no output schema, though some phrasing 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?

Given the absence of an output schema, the description fully covers return fields, source formats, override behavior, failure states, environment-variable availability, and the correct manual paths for secret changes. An agent has enough context to call the tool and interpret its results correctly.

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?

The input schema has 100% description coverage for both optional parameters, so the schema already explains workspace and environment defaults. The description does not add parameter-specific semantics beyond those schema descriptions, which is acceptable given the high coverage baseline.

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 description states a specific verb and resource: list secret variable names and their sources, never values. It names the returned fields (key, sensitive, updated_at, source, active) and explains source semantics, making the tool's scope unambiguous.

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 explains when to use the tool (to discover available secret names and sources), when mutation is impossible for agents (dashboard only, owner/admin required), and what to do when a secret is missing or a source is failing. It also explicitly tells the agent never to ask for pasted secret values.

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

All Runcrate tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.