Skip to main content
Glama
SourceParts

Source Parts MCP Server

Official
by SourceParts

ecn_update

Update an existing ECN's metadata or body by specifying only the fields to change. Optionally commit and create a pull request.

Instructions

Update metadata or body of an existing ECN.

The API clones the repo, modifies the ECN file, commits, and optionally creates a PR. Only the fields you provide will be changed. For local projects, use: parts project ecn update ECN-006 --status CLOSED

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesSource Parts project ID or git repo URL
ecn_idYesECN identifier (e.g. 'ECN-006')
statusNoNew status (OPEN, IN REVIEW, APPROVED, IMPLEMENTED, CLOSED)
severityNoNew severity (CRITICAL, HIGH, MEDIUM, LOW)
dispositionNoNew disposition (REQUIRED, RECOMMENDED, OPTIONAL)
titleNoNew title
categoryNoNew category
affectedNoNew affected components
sourceNoNew source reference
bodyNoNew body content (replaces entire body)
create_prNoIf True, create a PR with the change
branchNoTarget branch for the commit

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Since no annotations exist, the description carries full burden and reveals key behaviors: cloning the repo, modifying the ECN file, committing, and optionally creating a PR. This goes beyond the schema and helps set expectations. However, it lacks details on permissions or potential 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?

Very concise: two sentences plus a helpful CLI example. The purpose is front-loaded, and every sentence provides value. No extraneous text.

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 tool's complexity (12 parameters) and no annotations, the description covers core behavior and side effects adequately. The presence of an output schema relieves the need to explain return values. Minor gap: no mention of prerequisites or error conditions.

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% with descriptions for each parameter. The description adds limited value by stating that only provided fields change, but does not elaborate on parameter formats or interactions. 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?

Clearly states 'Update metadata or body of an existing ECN' with specific verb and resource. The description further explains the underlying process (clone, modify, commit, PR) which adds clarity and distinguishes it from create or get operations.

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?

Provides some usage hints ('Only the fields you provide will be changed' and a CLI example for local projects), but does not explicitly state when to choose this tool over siblings like ecn_create or ecn_get. No direct comparison with alternatives.

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/SourceParts/parts-mcp'

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