create_component
Create a new component entity to register coherent units of functionality as systems, services, APIs, databases, libraries, or tools, with optional dependencies and aliases for context filtering.
Instructions
Create a new Component entity.
A Component is any coherent unit of functionality that you hold context
about: an internal subsystem, an external service, an API, a database,
a library, or a tool. The kind tag lets you filter later.
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": {
"slug": "<slug>"
},
"name": "create_component"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| kind | No | one of "system" | "service" | "api" | "database" | "library" | "tool". Default "system" (generic fallback). | system |
| slug | Yes | lowercase a-z0-9- identifier (e.g. "api-gateway"). | |
| uses | No | optional list of component slugs this component depends on. Used by suggest_task_links for graph traversal. | |
| aliases | No | optional short nicknames (e.g. ["gw", "the gateway"]). Must be globally unique across all entities. | |
| governance | No | optional list of governance refs that apply to this component (e.g. ["governance:security-policy"]). | |
| description | No | one-paragraph prose description. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||