Skip to main content
Glama

create_change

Creates a named OpenSpec planning change in the configured repository, letting teams plan work without implementing or publishing code.

Instructions

Create a named OpenSpec planning change in the configured repository. Does not implement or publish code.

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

Input Schema

NameRequiredDescriptionDefault
idYes
workspacePathNoTrusted absolute project path from this chat; pass on every call. null selects personal storage. Omission uses only the environment default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare this is a non-read-only, non-destructive, closed-world operation. The description adds meaningful context that it creates a planning artifact rather than implementing or publishing code, but it does not disclose collision behavior, permissions, or what happens if the named change already exists.

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?

The definition is two short sentences with the core action front-loaded and a clear scope boundary second. There is no redundant wording or unnecessary detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter creation tool with annotations and no output schema, the description is adequate at a high level. It still leaves important gaps around the required id, duplicate handling, and the result of creation, which an agent would need for confident invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema fully describes workspacePath but leaves the required id parameter undocumented. The description only implies that id is a name via 'named OpenSpec planning change' and does not explain id format, uniqueness, or whether it may overwrite existing data.

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 states a specific verb and resource: create a named OpenSpec planning change in the configured repository. It also adds a useful scope boundary by saying it does not implement or publish code, though it does not explicitly differentiate itself from sibling tools such as read_change or validate_change.

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 is implied by 'Create a named OpenSpec planning change' and the exclusion 'Does not implement or publish code,' which helps distinguish planning creation from implementation. However, it gives no explicit when-to-use guidance versus alternatives like archive_change, read_change, or validate_change.

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