Skip to main content
Glama

read_mcdev_project_config

Reads the complete unredacted .mcdevrc.json from an absolute mcdev project root and returns its raw text, while excluding .mcdev-auth.json.

Instructions

Read the complete, UNREDACTED .mcdevrc.json, including credentials and custom fields, from a canonical absolute project root. Returns original raw text; never reads .mcdev-auth.json.

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

Input Schema

NameRequiredDescriptionDefault
workspaceRootYesAbsolute path to the mcdev project root containing `.mcdevrc.json`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv0.1.1

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does well: it discloses that credentials are included, that raw text is returned, and that `.mcdev-auth.json` is never read. It does not describe failure behavior if the file is missing or inaccessible, which prevents a 5.

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 tightly written sentences with no waste. The key distinction—unredacted output—is front-loaded, and the auth file exclusion follows immediately.

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 simple one-parameter read tool with no output schema, the description covers return format and scope sufficiently. It would be stronger if it mentioned behavior when the config file is absent or unreadable, but no critical decision information is missing.

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 coverage is 100% and the single `workspaceRoot` parameter is already documented as an absolute path to the mcdev project root. The description reinforces 'canonical absolute project root' but adds no syntax or validation details 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?

The description states a specific verb (read) and resource (`.mcdevrc.json`), and distinguishes this from the auth file explicitly. It also specifies the scope: complete, unredacted contents, raw text, from a canonical absolute project root.

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?

The description makes clear when this tool is appropriate: when the full unredacted config is needed. It does not explicitly name the sibling alternatives such as `preview_mcdev_project_config` or `diagnose_mcdev_project_config`, but the 'UNREDACTED' framing strongly implies the distinction.

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