Skip to main content
Glama
restforge

@restforge-dev/mcp-server

Official
by restforge
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

Read Database Connection Env

setup_read_env
Read-onlyIdempotent

Verify current configuration settings of a RESTForge project by reading the db-connection.env file, with sensitive data automatically masked.

Instructions

Read and parse the config/db-connection.env file, returning all parameters as KEY=value lines. Sensitive fields (LICENSE, DB_PASSWORD, REDIS_PASSWORD, KAFKA_SASL_PASSWORD) are masked by default.

USE WHEN:

  • The user asks to see the active/current configuration, parameters, settings, or env values of a RESTForge project

  • The user asks questions like "tampilkan parameter yang aktif", "config apa yang sudah di-set", "show current settings", "cek konfigurasi", "what's configured in this project"

  • Verifying the current configuration before calling 'setup_write_env' or 'setup_update_env' to make changes

  • Auditing the active config after a change

  • Listing every parameter present in the file (including optional sections like Live Sync, Redis, Kafka, Logging)

  • Checking whether a RESTForge project has been set up at all (this tool returns a clear "file not found" precondition if not)

DO NOT USE FOR:

  • Writing values -> use 'setup_write_env' or 'setup_update_env'

  • Validating connection -> use 'setup_validate_config'

This tool is READ-ONLY and safe to call repeatedly. Pass unmask=true to see real values of sensitive fields (use with care).

PRESENTATION GUIDANCE:

  • Match the user's language. If the user writes in Indonesian, respond in Indonesian.

  • Never mention internal tool names in the reply to the user. Describe actions by what they do (e.g. "set up the initial config", "fill in the credentials", "update a single value", "validate the connection").

  • Speak in plain language. Summarise the result; do not paste the full KEY=value list unless the user explicitly asks for it.

  • Even when unmask=true, do not echo sensitive values (license keys, passwords) into chat unless the user explicitly asks. Prefer to confirm presence and length only.

  • When a precondition is not met (e.g. config file is missing), frame it as a question or next-step suggestion rather than an error.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cwdYesAbsolute path of the project folder
configFileNoConfig file name in the config/ folder. Default: db-connection.envdb-connection.env
unmaskNoWhen true, show real values of sensitive fields (LICENSE, *_PASSWORD). Default: false

Tool Definition Quality

A4.8/5.0
Behavior5/5

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

Annotations mark readOnlyHint and idempotentHint; description adds that the tool is read-only, safe to repeat, masks sensitive fields by default, and the unmask parameter behavior. No contradiction.

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?

Well-organized with clear sections but slightly long; some redundancy (e.g., 'READ-ONLY' repeated). Still effective and easy to scan.

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?

Perfectly complete: covers purpose, usage, parameters, behavior, presentation, and error conditions. No gaps considering the tool's role and lack of 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 covers all 3 parameters with descriptions. Description adds guidance on unmask usage and default masking, enhancing understanding beyond the schema.

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?

Title and description clearly specify the action (read and parse) and resource (config/db-connection.env). Distinguishes from siblings like setup_write_env, setup_update_env, and setup_validate_config by name and scope.

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?

Explicit 'USE WHEN' list covering multiple scenarios and 'DO NOT USE FOR' with alternative tools. Also includes presentation guidance for safe interaction.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/restforge/restforge-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server