Skip to main content
Glama
GuangminJu

mellos-mapping

by GuangminJu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

View the current map

mmap_view

Render the current Mellos map as monochrome text to inspect map state or show it inline in conversation. The output's pages line reveals which pages exist and which you are viewing, so you can discover maps without probing files.

Instructions

Render the current Mellos map as monochrome text — the same picture the split-pane watcher shows live. Use it to check the map state or to show it inline in conversation. Every response ends with a pages: line naming the pages this project actually has and which one you are looking at, so this is also how you discover whether a map exists at all and under which slugs — never probe the files.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNopage (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.
zoomNozoom ladder: 1 = detail (notes unfold), 0 = standard (default), -1..-3 = scaled down, -4 = overview glyphs

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.26.0
    • 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."
    • changedInput schema / properties / zoom / maximum
      Previous value: -1New value: +2
  2. First observedv0.12.0

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden. It discloses the output style (monochrome text, same as the live watcher), the guaranteed `pages:` trailing line, and that it can reveal map existence. It stops short of explicitly stating it has no side effects or describing missing-map behavior, but 'view/render' strongly implies read-only.

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?

Two sentences, front-loaded with purpose, then usage and behavioral notes. The split-pane watcher comparison and the `pages:` detail are informative rather than padding.

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 read-only view tool with no output schema, the description covers the return format (text plus `pages:` line), when to use it, and its discovery role. It could add explicit no-mutation wording or missing-map behavior, but nothing critical is absent for correct invocation.

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 100% and both `page` and `zoom` have detailed inline descriptions, so the tool description adds no additional parameter semantics. The baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Render'), resource ('current Mellos map'), and output format ('monochrome text'), and clarifies its secondary role in discovering pages and slugs. It doesn't explicitly contrast with sibling mmap_read, but the action is unambiguous.

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?

Explicitly says when to use it: to check map state, show inline in conversation, and discover whether a map exists and under which slugs. It also provides an exclusion ('never probe the files') and, in the page parameter, directs reading existing pages with mmap_read first.

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

Deploy Server

Other Tools