cursor-mcp

Cursor: validate environment definition

cursor_validate_environment_definition

Read-onlyIdempotent

Validate a Cursor environment definition against the published schema. Get separate reports for schema errors, safety warnings, and capability limitations.

Instructions

Check a Cursor environment definition against the published schema. Schema errors, safety warnings, and capability limitations are reported separately.

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

Input Schema

Name	Required	Description	Default
`definition`	Yes	One definition: either a repository root or the document text.
`syncTarget`	No	Ask for a synchronization request for Environment Operations. Never a Save.

Output Schema

Name	Required	Description	Default
`trust`	Yes
`errors`	No
`origin`	Yes
`safety`	No
`source`	Yes
`status`	Yes
`limitations`	No
`syncRequest`	No
`errorsTruncated`	Yes
`safetyTruncated`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.6.0Sep 9, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, covering the safety profile. The description adds value by disclosing that results are reported in separate categories. It does not mention the optional syncTarget behavior, but the schema documents that and annotations indicate no destructive side effects.

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?

A single, tight sentence states the action and the key output categories with no filler. The most important information is front-loaded and every word earns its place.

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?

Given the rich input schema, output schema, and safety annotations, the description covers the essential behavioral context. The only minor gap is not surfacing the optional syncTarget capability, but that is already documented in the schema and is not required for basic validation usage.

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 description coverage is 100%, and the schema already provides detailed descriptions for definition, source, repoRoot, and syncTarget. The description itself adds no parameter-level meaning, so the baseline score of 3 is appropriate.

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 clearly states the tool checks a Cursor environment definition against the published schema and explicitly lists the three reporting categories (schema errors, safety warnings, capability limitations). This is specific enough to distinguish it from sibling tools like inspect_environment_definition or diff_environment_definition.

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?

Usage context is implied: use this tool when you need to validate a definition against the schema. However, the description provides no explicit when-to-use guidance, exclusions, or references to alternative sibling tools.

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