Skip to main content
Glama

domain_modeling

Create and refine conceptual domain models by defining entities, relationships, and rules to clarify complex domains and solve ambiguity.

Instructions

Creating and refining conceptual models of a domain, including entities, relationships, and rules.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stageYesThe current stage of the modeling process.
entitiesYesA list of all entities in the domain.
paradigmYesThe modeling paradigm used.
useCasesNoA list of use cases for the domain.
iterationYesThe iteration number of this modeling session.
boundariesNoThe bounded context of the domain.
domainNameYesThe name of the domain being modeled.
modelingIdYesA unique identifier for this modeling session.
assumptionsNoA list of assumptions made during the modeling process.
descriptionYesA detailed description of the domain.
domainRulesNoA list of all domain rules.
stakeholdersNoA list of stakeholders involved in the modeling process.
modelingNotesNoA list of notes related to the modeling process.
relationshipsNoA list of all relationships between entities.
modelValidationNoValidation results for the model.
nextStageNeededYesA flag indicating whether another modeling stage is required.
abstractionLevelYesThe level of abstraction of the model.
suggestedNextStageNoThe suggested next stage in the modeling process.
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It does not state whether the tool mutates state, persists, or requires authentication. It merely defines the modeling action without revealing side effects or limitations.

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 description is extremely concise: one sentence that clearly communicates the core purpose. It front-loads the action and key concepts with no wasted words.

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

Completeness2/5

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

Given the tool's complexity (18 parameters, nested objects, no output schema), the description is too brief. It fails to explain the modeling stages, process flow, or what the tool returns, making it incomplete for effective use.

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%, so all parameters are documented. The description mentions 'entities, relationships, and rules' which correspond to schema fields, but adds no extra meaning. Baseline 3 is appropriate since the schema already does the work.

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?

The description clearly states it is for 'creating and refining conceptual models of a domain, including entities, relationships, and rules.' This specific verb+resource combination distinguishes it from sibling tools like 'collaborative_reasoning' or 'problem_decomposition' which are general reasoning approaches.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. It lacks explicit context, prerequisites, or when-not-to-use instructions. The description only states the tool's function without any usage pointers.

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/emmahyde/thinking-patterns'

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