You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/cmd/root.go
+15-1Lines changed: 15 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -31,6 +31,8 @@ type serializedComponent struct {
31
31
Ownerstring
32
32
Urlstring
33
33
LevelserializedLevel
34
+
LifecycleserializedLifecycle
35
+
TierserializedTier
34
36
}
35
37
36
38
typeserializedInfrastructureResourcestruct {
@@ -47,6 +49,16 @@ type serializedLevel struct {
47
49
Indexint
48
50
}
49
51
52
+
typeserializedLifecyclestruct {
53
+
Aliasstring
54
+
Indexint
55
+
}
56
+
57
+
typeserializedTierstruct {
58
+
Aliasstring
59
+
Indexint
60
+
}
61
+
50
62
typeserializedCheckstruct {
51
63
Idstring
52
64
Namestring
@@ -168,7 +180,7 @@ var rootCmd = &cobra.Command{
168
180
s.AddTool(
169
181
mcp.NewTool(
170
182
"components",
171
-
mcp.WithDescription("Get all the components in the OpsLevel account. Components are objects in OpsLevel that represent things like apis, libraries, services, frontends, backends, etc. Use this tool to list what components are in the catalog, what team is the owner, what primary coding language is used, and what primary framework is used. It also includes its rubric level, corresponding to the maturity of the component; a higher index is better. A level is achieved by passing all checks tied to that same level."),
183
+
mcp.WithDescription("Get all the components in the OpsLevel account. Components are objects in OpsLevel that represent things like apis, libraries, services, frontends, backends, etc. Use this tool to list what components are in the catalog, what team is the owner, what primary coding language is used, and what primary framework is used. It also includes its rubric level, corresponding to the maturity of the component; a higher index is better. A level is achieved by passing all checks tied to that same level. The Lifecycle field indicates the stage of the component (e.g., Alpha, Beta, GA, Decommissioned). The Tier field represents the importance and criticality of the component, with Tier 1 being the most critical (customer-facing with high impact) and Tier 4 being of least importance."),
0 commit comments