apex-memory

create_domain

Create a new owner-only knowledge domain with index, status, log, and decision pages, plus a summary of what it stores and when to use it.

Instructions

Create a new domain with its start pages: index (with the catalog), status, log and decisions. description is the domain's line in list_domains: what it holds and when to choose it (e.g. "not for X; use Y"); it is kept as the index summary. domain: lowercase letters, digits and hyphens. Owner only.

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": {
      "domain": "<domain>",
      "title": "<title>",
      "description": "<description>"
    },
    "name": "create_domain"
  }
}

Input Schema

Name	Required	Description	Default
`title`	Yes
`domain`	Yes
`task_id`	No
`description`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.1Nov 3, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations supplied, the description carries real disclosure burden and mostly meets it: it says exactly what gets created as side effects (four start pages including a catalog), and flags the owner-only permission requirement. It does not state failure behavior for a duplicate domain name or whether the operation is reversible, which keeps it short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the action and side effects, then constraints, then the permission gate — a sensible order with no filler. The middle sentence is a tangled run-on that separates the field name from its meaning awkwardly, costing a point on readability.

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

Completeness3/5

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

For a mutation tool with no annotations, no output schema, and 0% schema coverage across four parameters, the description covers effects and permissions well but leaves `title` and `task_id` entirely unexplained. An agent can call it correctly for the three required fields but must guess at the optional `task_id` linkage.

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 description coverage is 0%, so the description must compensate, and it partly does: it gives the format constraint for `domain` (lowercase letters, digits, hyphens) and explains the purpose of `description` (the line shown in list_domains, retained as the index summary). It says nothing about `title` or `task_id`, leaving half the parameters undocumented in both schema and description.

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?

States a specific verb and resource ("Create a new domain") and immediately names the artifacts created alongside it — index with catalog, status, log, decisions — so the agent knows this is a scaffolding operation, not a bare insert. It also anchors the result against the sibling tool list_domains, clarifying where the new entry will surface.

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

Usage Guidelines3/5

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

Usage is implied by the verb and gated by "Owner only," which tells the agent this is a privileged operation. However, there is no explicit statement of when to create a new domain versus working within an existing one, and no guidance on what to do if the domain already exists. The guidance about "not for X; use Y" applies to the description field content, not to selecting this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server