Skip to main content
Glama
marvkr

Better Design

by marvkr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Update the Feature Map

update-feature-map
Read-onlyIdempotent

Apply a single change to the feature map and get the updated file back, so features and flows stay in step with the code after additions, renames, removals, or step changes.

Instructions

Apply one change to the feature map and get the new file back. Call it after you add, rename or remove a feature or a flow, or change a flow's steps, so the map stays in step with the code.

Changes, one per call:

  • { op: "add-feature", name, description?, flows? }

  • { op: "rename-feature", feature, name }

  • { op: "remove-feature", feature }

  • { op: "set-flow", feature, flow: { name, description?, steps: [{ name, route?, screen?, action?, components?, data? }] } } adds the flow, or replaces the one with that name

  • { op: "rename-flow", feature, flow, name }

  • { op: "remove-flow", feature, flow }

The Main Quest is the one goal for a set time, with at most 3 initiatives that carry it out. When the user names a direction ("this quarter is about team planning"), save it:

  • { op: "set-main-quest", goal (12 words at most), ends: "YYYY-MM-DD", starts?, initiatives?: [{ name, outcome }] } refused while another is open

  • { op: "end-main-quest" }

  • { op: "add-initiative", name, outcome (one sentence, 25 words at most) }

  • { op: "remove-initiative", initiative }

  • { op: "set-initiative", feature, flow?, initiative } links work to an initiative, to "foundation" for upkeep such as sign-in and billing, or null to unlink

feature and flow take an id or an exact name. Write the returned file to .better-design/feature-map.json.

Input Schema

NameRequiredDescriptionDefault
mapYesThe exact contents of .better-design/feature-map.json.
changeYes
contextNoOptional. One sentence on WHY you are calling this and what the user asked for (e.g. 'adding nav icons for the fintech dashboard'). Used only for usage analytics; does not change the result.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

The description is consistent with the annotations: it never claims to write to disk, only to return the new file for the caller to write, which matches readOnlyHint=true. It adds behavior the annotations cannot express: set-flow 'adds the flow, or replaces the one with that name' (idempotent semantics), set-main-quest is 'refused while another is open,' and it documents word/date constraints per operation.

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?

The core behavior is front-loaded in the first sentence and the per-op list is structured and scannable. It is long, and some entries restate field names already in the schema, but nearly every line carries non-obvious semantics.

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

Completeness5/5

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

There is no output schema, and the description covers the return value ('get the new file back') plus the required follow-up ('Write the returned file to .better-design/feature-map.json'). With a 12-variant discriminated union, the op-by-op documentation makes the definition complete for correct invocation.

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

Parameters5/5

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

Schema coverage is only 67%, yet the description fully compensates by documenting the discriminator values of 'change' and the field shape each op expects. It also explains semantics the schema cannot: 'feature' and 'flow' accept an id or exact name, 'foundation' is a special initiative value, and null unlinks.

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 and resource ('Apply one change to the feature map and get the new file back'), and the operation list makes the scope unambiguous. It does not explicitly distinguish itself from the siblings build-feature-map or read-feature-map, so an agent must infer the distinction from the verb.

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

Usage Guidelines4/5

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

Gives clear triggering conditions ('Call it after you add, rename or remove a feature or a flow, or change a flow's steps') and explains the goal ('so the map stays in step with the code'). It also specifies when to record a Main Quest. There is no explicit when-not-to-use or named alternative tool.

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