md-doc

environment_get

Detalle de un entorno por nombre: descripción y NOMBRES de variables (sin valores) y el comando para usarlo. 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

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

Input Schema

Name	Required	Description	Default
`name`	Yes	Nombre del entorno, p. ej. "mi-app.es"

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 behavioral burden and succeeds: it states values never reach the agent, output is masked, exit code 3 means locked, CLI install/login steps, and that it cannot change/delete values or create environments. These are concrete operational constraints an agent must know.

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 purpose is front-loaded and the safety rules are numbered, so the structure is clear. It is somewhat long and includes CLI install/login details that may be better placed elsewhere, but the length is largely justified for a secrets-related tool.

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?

No output schema or annotations are supplied, so the description must define returns and safety behavior, which it does: description, variable names without values, and the command. It also covers blocked CLI, missing variables, and write limitations, leaving little material ambiguity for this one-param 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?

The single name parameter is fully described in the schema with an example. The description adds only that retrieval is by name, without new format, validation, or lookup semantics beyond the schema.

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 first sentence states a specific operation: detail of one environment by name, returning description, variable NAMES without values, and the usage command. It clearly differs from a list operation by requiring a name, though it does not explicitly point to environments_list.

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?

It explains how to use the returned environment (mddoc run) and when to use environment_variables_add for missing variables, but it does not explicitly say when to choose this tool over environments_list or other ways to inspect an environment. Selection guidance is therefore implied rather than spelled out.

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?