cursor-mcp

Cursor: get environment configuration

cursor_get_environment_configuration

Read-onlyIdempotent

Retrieve an environment's configuration candidates, source, precedence, and digest via the Cursor CLI to verify setup and keep scripts digest-based.

Instructions

Read one environment's configuration candidates, source, precedence, and digest through a configured Cursor CLI. Scripts stay digests.

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

Input Schema

Name	Required	Description	Default
`environmentPublicId`	Yes	Public opaque environmentPublicId, as cursor_list_environments reports it. Never a numeric internal id.

Output Schema

Name	Required	Description	Default
`cli`	Yes
`reason`	No
`status`	Yes
`catalog`	No
`nextSteps`	No
`environments`	No
`configuration`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.6.0Sep 9, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive flags. The description adds meaningful context beyond annotations by noting the dependency on a configured Cursor CLI and specifying the data fields read (candidates, source, precedence, digest). The cryptic 'Scripts stay digests' is the only weak point.

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

Conciseness3/5

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

The description is short and front-loaded, but the second sentence 'Scripts stay digests' is unclear and does not earn its place. It adds confusion rather than value, making the overall structure only partially effective.

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?

With an output schema present, return values need not be explained. The description covers the operation's scope and prerequisite (configured CLI), and annotations handle safety. The cryptic final phrase is the only gap; otherwise the definition is sufficiently complete for an agent to call it 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?

Schema coverage is 100% and the parameter description is already detailed, clarifying how to obtain environmentPublicId from cursor_list_environments. The tool description does not add additional parameter semantics beyond what the schema provides, so a baseline score of 3 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 description clearly states the action ('Read') and resource ('one environment's configuration candidates, source, precedence, and digest'), distinguishing it from list-type siblings. The phrase 'through a configured Cursor CLI' adds a prerequisite context. However, 'Scripts stay digests' is cryptic and slightly detracts from clarity.

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?

The description implies use for a single environment's config, contrasting with list_environments, but does not explicitly state when to use this tool over alternatives or when not to use it. There is no mention of exclusions or alternative tools, leaving routing partially to inference.

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