mellos-mapping

Overview Schema Source Related Servers Discussions Admin

Declare map structure

mmap_declare

Declare a layered map's structure—title, diagram kind, layers, lanes, groups, nodes, and downward dependency edges—in a single all-or-nothing batch.

Instructions

Grow the Mellos map: set the title and diagram kind, add layer bands, lanes and groups (labeled subsystems within ONE band — declare them when a single band grows crowded, roughly five or more nodes in that band; a group must be a strict subset of its band, and a map spread thin across many bands needs none), add nodes, add dependency edges. Declare the missing design after reading existing pages with mmap_read; reuse verified nodes. Edges must point strictly downward (a node may only use nodes on lower layers); the batch is all-or-nothing. Title and kind can also be changed with mmap_update; this legacy form remains supported. Revising what already exists (moving, renaming, relabeling, clearing) is mmap_update.

Input Schema

TableJSON Schema

Name	Required	Description
`kind`	No	diagram kind. dev (default) = the live progress ledger with status skins. The rest are documentation diagrams rendered neutrally: architecture (layered components; also fits call graphs and module dependencies), dataflow (source→transform→sink, stages as layers), behavior-tree (root on top, leaves at the bottom; also fits mind maps and WBS), sequence (classic call/return: rank = time step with rank 0 = EARLIEST, drawn top-down; declare lanes as participants and make every call AND every return its own event node in the acting participant's lane, edges labeled with the message). State machines are unsupported: cycles cannot enter a Mellos map.
`page`	No	page (parallel map) this call targets; omit for the default page. A new conversation is not a new effort. Read existing pages with mmap_read first; reuse the same page for continued work. Create a new page only for a distinct effort.
`edges`	No
`lanes`	No	vertical columns crossing all bands; declaration order = left-to-right
`nodes`	No
`title`	No	map title, e.g. the feature being built; null removes it
`groups`	No
`layers`	No
`context`	No
`expectedRevision`	No	Revision from mmap_read; absent requires a new page. A stale revision returns CONFLICT.

Schema Changelog

Changes observed during successful MCP inspections.

Changed44 schema fields changedv0.26.0Sep 19, 2026

addedInput schema / properties / context

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "next": {
+      "description": "Next actions for resuming this effort",
+      "maxLength": 2000,
+      "minLength": 1,
+      "pattern": "^[^\\u0000-\\u0008\\u000b-\\u001f\\u007f-\\u009f]*$",
+      "type": "string"
+    },
+    "summary": {
+      "description": "Concise purpose and confirmed decisions",
+      "maxLength": 2000,
+      "minLength": 1,
+      "pattern": "^[^\\u0000-\\u0008\\u000b-\\u001f\\u007f-\\u009f]*$",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

addedInput schema / properties / edges / items / properties / label / minLength
```
Added value: +1
```
addedInput schema / properties / edges / items / properties / label / pattern
```
Added value: +"^[^\\u0000-\\u001f\\u007f-\\u009f]*$"
```

addedInput schema / properties / expectedRevision

Added value: +{
+  "description": "Revision from mmap_read; absent requires a new page. A stale revision returns CONFLICT.",
+  "pattern": "^(?:[a-f0-9]{64}|absent)$",
+  "type": "string"
+}

removedInput schema / properties / groups / items / properties / id / $ref
```
Removed value: -"#/properties/page"
```
addedInput schema / properties / groups / items / properties / id / description
```
Added value: +"stable kebab-case identifier of the group"
```
addedInput schema / properties / groups / items / properties / id / pattern
```
Added value: +"^[a-z0-9][a-z0-9-]{0,63}$"
```
addedInput schema / properties / groups / items / properties / id / type
```
Added value: +"string"
```
addedInput schema / properties / groups / items / properties / label / pattern
```
Added value: +"^[^\\u0000-\\u001f\\u007f-\\u009f]*$"
```
removedInput schema / properties / lanes / items / properties / id / $ref
```
Removed value: -"#/properties/page"
```
addedInput schema / properties / lanes / items / properties / id / description
```
Added value: +"stable kebab-case identifier of the lane"
```
addedInput schema / properties / lanes / items / properties / id / pattern
```
Added value: +"^[a-z0-9][a-z0-9-]{0,63}$"
```
addedInput schema / properties / lanes / items / properties / id / type
```
Added value: +"string"
```
addedInput schema / properties / lanes / items / properties / label / pattern
```
Added value: +"^[^\\u0000-\\u001f\\u007f-\\u009f]*$"
```
removedInput schema / properties / layers / items / properties / id / $ref
```
Removed value: -"#/properties/page"
```
addedInput schema / properties / layers / items / properties / id / description
```
Added value: +"stable kebab-case identifier of the band"
```
addedInput schema / properties / layers / items / properties / id / pattern
```
Added value: +"^[a-z0-9][a-z0-9-]{0,63}$"
```
addedInput schema / properties / layers / items / properties / id / type
```
Added value: +"string"
```
addedInput schema / properties / layers / items / properties / name / pattern
```
Added value: +"^[^\\u0000-\\u001f\\u007f-\\u009f]*$"
```

changedInput schema / properties / layers / items / properties / rank / description

Previous value: -"0 = bottom / most primitive; must be unique"New value: +"an integer in 0..99, 0 = bottom / most primitive; must be unique among the map's bands"

addedInput schema / properties / nodes / items / properties / detail / minLength
```
Added value: +1
```
addedInput schema / properties / nodes / items / properties / detail / pattern
```
Added value: +"^[^\\u0000-\\u0008\\u000b-\\u001f\\u007f-\\u009f]*$"
```

addedInput schema / properties / nodes / items / properties / evidence

Added value: +{
+  "description": "how an already-verified node was verified; for regressed: what broke. Declaring a node straight to done needs it as much as updating one does.",
+  "maxLength": 200,
+  "minLength": 1,
+  "pattern": "^[^\\u0000-\\u001f\\u007f-\\u009f]*$",
+  "type": "string"
+}

removedInput schema / properties / nodes / items / properties / group / $ref
```
Removed value: -"#/properties/page"
```
addedInput schema / properties / nodes / items / properties / group / pattern
```
Added value: +"^[a-z0-9][a-z0-9-]{0,63}$"
```
addedInput schema / properties / nodes / items / properties / group / type
```
Added value: +"string"
```
removedInput schema / properties / nodes / items / properties / id / $ref
```
Removed value: -"#/properties/page"
```
addedInput schema / properties / nodes / items / properties / id / description
```
Added value: +"stable kebab-case identifier of the node"
```
addedInput schema / properties / nodes / items / properties / id / pattern
```
Added value: +"^[a-z0-9][a-z0-9-]{0,63}$"
```
addedInput schema / properties / nodes / items / properties / id / type
```
Added value: +"string"
```
addedInput schema / properties / nodes / items / properties / label / pattern
```
Added value: +"^[^\\u0000-\\u001f\\u007f-\\u009f]*$"
```
removedInput schema / properties / nodes / items / properties / lane / $ref
```
Removed value: -"#/properties/page"
```
addedInput schema / properties / nodes / items / properties / lane / pattern
```
Added value: +"^[a-z0-9][a-z0-9-]{0,63}$"
```
addedInput schema / properties / nodes / items / properties / lane / type
```
Added value: +"string"
```

addedInput schema / properties / nodes / items / properties / sources

Added value: +{
+  "description": "Optional source files and verified SHA256 baselines. mmap_read changes checks them without rescanning the repository.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "path": {
+        "maxLength": 1024,
+        "type": "string"
+      },
+      "sha256": {
+        "pattern": "^[a-f0-9]{64}$",
+        "type": "string"
+      }
+    },
+    "required": [
+      "path"
+    ],
+    "type": "object"
+  },
+  "maxItems": 100,
+  "type": "array"
+}

changedInput schema / properties / nodes / items / properties / status / description

Previous value: -"defaults to planned"New value: +"defaults to planned. planned = ghost on the map; in-progress = spinner; done = verified; regressed = was done, now broken"

removedInput schema / properties / nodes / items / properties / submap / $ref
```
Removed value: -"#/properties/page"
```
addedInput schema / properties / nodes / items / properties / submap / pattern
```
Added value: +"^[a-z0-9][a-z0-9-]{0,63}$"
```
addedInput schema / properties / nodes / items / properties / submap / type
```
Added value: +"string"
```

changedInput schema / properties / page / description

Previous value: -"page (parallel map) this call targets; omit for the default page. One effort = one page: start a NEW effort on its own page named after the effort, so concurrent sessions never write over each other and the pane can switch between pages."New value: +"page (parallel map) this call targets; omit for the default page. A new conversation is not a new effort. Read existing pages with mmap_read first; reuse the same page for continued work. Create a new page only for a distinct effort."

addedInput schema / properties / title / anyOf

Added value: +[
+  {
+    "description": "map title, e.g. the feature being built; null removes it",
+    "maxLength": 120,
+    "minLength": 1,
+    "pattern": "^[^\\u0000-\\u001f\\u007f-\\u009f]*$",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / title / description

Previous value: -"map title, e.g. the feature being built"New value: +"map title, e.g. the feature being built; null removes it"

removedInput schema / properties / title / maxLength
```
Removed value: -120
```
removedInput schema / properties / title / type
```
Removed value: -"string"
```

First observedv0.12.0Aug 13, 2026

TDQS

A4.6/5.0

Behavior4/5

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

With no annotations, the description takes on the behavioral burden and does substantial work: it discloses the strict downward-edge rule, the all-or-nothing batch semantics, and the strict-subset rule for groups. It does not mention response/conflict behavior, but the transaction and constraint disclosures go well beyond the schema.

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 front-loaded with the purpose and operates at the right level of abstraction; the parenthetical group rule is dense but directly actionable. No sentences repeat schema boilerplate.

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

Completeness4/5

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

For a 10-parameter, four-array tool with no annotations and no output schema, this description explains workflow, scope split with mmap_update, and critical constraints, while the schema covers parameter details. The main missing piece is return/conflict behavior, but the rest is unusually complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already describes most parameters well, and the description adds helpful operational semantics: when groups are warranted (five or more nodes in a band), that they must be strict subsets, and that edges must point strictly downward. This adds usable meaning without re-listing every field.

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 uses a concrete verb ('Grow') and lists the exact map objects it creates (title, kind, bands, lanes, groups, nodes, edges). It also contrasts with mmap_update, saying revision of existing content is update, so the tool's scope is unambiguous next to siblings.

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

Usage Guidelines5/5

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

It explicitly tells the agent to read with mmap_read before declaring and to reuse verified nodes. It names mmap_update as the alternative for revising existing content and even notes that title/kind changes are supported here only as a legacy path, giving both a primary and exclusionary usage signal.

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

Deploy Server

Declare map structure

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools