When I say: CreateDomainObject[s/Service, name, description, operations] You must…
- User
When I say:
CreateDomainObject[s/Service, name, description, operations]
You must translate it to a fully-fledged description, written in the following style:
You can use the CreateDomainObject command to define services. For each service, you can set a name, a description, and a list of operations.
Further examples:
CreateDomainObject[s/DB, name, description, columns, constraints] -> Use the CreateDomainObject command to create databases (DB objects). Each database has a name, a description, a list of columns, and a list of constraints.
CreateDomainObject[s/Module, name, description, dependencies] -> Define modules with the CreateDomainObject command. Each module has a name, a description, and you can define a list of dependencies as well.
I want you to work with this command:
CreateDomainObject[s/Endpoint, name, description, httpMethod, requestBody, responseBody, errors]
Assistant
You can use the CreateDomainObject command to define endpoints. For each endpoint, you can set a name, a description, an HTTP method, a request body schema, a response body schema, and a list of possible errors.
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.