md-doc

environments_list

Lista los entornos del usuario (p. ej. "mi-app.es") con los NOMBRES de sus variables, nunca los valores, y su carpeta (folderId, ver environment_folders_list). Entornos (variables de entorno/secretos): los valores NUNCA pasan por ti. Para usarlos ejecuta en la terminal mddoc run <entorno> -- <comando>: el CLI inyecta las variables en ese proceso y enmascara su salida. Reglas: (1) no intentes ver, imprimir, copiar, codificar ni volcar a fichero los valores (nada de printenv, env, echo $VAR, base64, > .env…); (2) si el comando termina con código 3 el CLI está bloqueado: detente y pide al usuario que ejecute mddoc unlock en su terminal; nunca le pidas el valor ni lo busques en otro sitio (.env, historial, notas); (3) si "mddoc" no existe, indica al usuario que instale el CLI (Linux o macOS, Node.js 20+) con npm install -g --prefer-online <URL de md-doc>/cli/mddoc.tgz (p. ej. https://app.md-doc.com/cli/mddoc.tgz; el comando exacto está en Entornos → Usar desde la terminal) y que conecte el equipo con mddoc login usando una API key de tipo CLI; (4) tú no escribes valores: si a un entorno existente le falta una variable, añade su NOMBRE con environment_variables_add (queda «pendiente de valor», mddoc run no la inyecta) y pide al usuario que la rellene en la web; si es un secreto aleatorio que puedes generar (contraseña, token, clave de cifrado), ejecuta mddoc set <entorno> <VARIABLE> --generate, que la crea cifrada sin mostrártela. Si el usuario te da un valor en el chat, no lo guardes tú: pídele que lo ponga en la web o con mddoc set <entorno> <VARIABLE> en su terminal. No puedes cambiar ni borrar valores existentes ni crear entornos.

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": "environments_list"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4/5.0

Behavior5/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 so: values are never returned or exposed, the CLI injects and masks them, exit code 3 means the CLI is locked and requires `mddoc unlock`, and the tool cannot create, modify, or delete anything. It also states prerequisites (Node.js 20+, mddoc login with a CLI API key), which is exactly the kind of context annotations would otherwise supply.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is front-loaded, but the bulk of the text is CLI workflow and installation instructions (npm install, unlock, set --generate, terminal commands) that belong to a general environment-usage policy rather than a zero-argument list tool. Rules (1) through (4) are security-relevant but far outweigh anything specific to this call.

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?

For a parameterless list tool with no output schema, it explains what is returned (environments, variable names, folderId) and what is deliberately withheld (values). It does not state ordering, pagination, or whether all environments are returned, which is a minor gap at this complexity level.

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?

The tool takes zero parameters, so there is no schema semantics to supplement; baseline is 4. The description does not add parameter detail because none exists, which is appropriate.

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 opening sentence gives a specific verb and resource: it lists the user's environments with the NAMES of their variables (never values) plus their folderId. It cross-references environment_folders_list for folders, but never distinguishes itself from environment_get, which likely returns a single environment, so sibling differentiation is only partial.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides explicit routing: use environment_folders_list for folder data, environment_variables_add to register a missing variable name, and `mddoc set --generate` for generated secrets, plus a clear exclusion ('No puedes cambiar ni borrar valores existentes ni crear entornos'). What is missing is guidance on when to call this versus environment_get when the user already names a specific environment.

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

All md-doc 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.

Resources

Need Help?