Create a new aggregate within a specified bounded context, defining its name, responsibilities, and knowledge level to model domain-driven design entities.
Create a new aggregate in a bounded context
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Name of the aggregate | |
| contextName | Yes | Name of the bounded context | |
| knowledgeLevel | No | Knowledge level | |
| responsibilities | No | List of responsibilities |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. Only says 'Create', no mention of side effects, permissions, idempotency, or behavior on duplicate names.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence is concise but at the expense of valuable information. Does not earn its place by adding utility beyond the name.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema and moderate complexity (4 params) demand more detail. Incomplete for a creation tool with many siblings.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema covers 100% of parameters; description adds no extra meaning beyond what's already in schema descriptions.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states verb 'Create' and resource 'aggregate in a bounded context', distinguishing from siblings like cml_create_bounded_context or cml_create_model.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool vs alternatives like cml_update_aggregate or other creation tools. No context on prerequisites or typical use cases.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/thijs-hakkenberg/contextmapper_mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server