Skip to main content
Glama

Better Design

by io.github.marvkr
OverviewDiscussionsAdmin

Read the Feature Map

read-feature-map
Read-onlyIdempotent

Returns the flows in a feature map that match a flow name, a feature or a file path, with the screen, route, components and data files of every step. Pass the contents of .better-design/feature-map.json as map. With no filter it lists every flow and the Main Quest, each initiative with what serves it. Pass planned to check new work against the Main Quest before building it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mapYesThe exact contents of .better-design/feature-map.json.
fileNoA file path or route; returns every flow that uses it.
flowNoA flow id or part of its name.
featureNoA feature id or part of its name.
plannedNoRoutes, file paths or names of work you are about to build; checks each against what the product already makes and the Main Quest.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / planned / description
      Previous value: -"Routes, file paths or names of work you are about to build; checks each against the Main Quest."New value: +"Routes, file paths or names of work you are about to build; checks each against what the product already makes and the Main Quest."
  2. Changed1 schema field changed
    • addedInput schema / properties / planned
      Added value: +{
+  "description": "Routes, file paths or names of work you are about to build; checks each against the Main Quest.",
+  "items": {
+    "maxLength": 500,
+    "minLength": 1,
+    "type": "string"
+  },
+  "maxItems": 50,
+  "type": "array"
+}
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds real value by explaining return content and the no-filter behavior, but no output schema exists and it doesn't mention the 2MB map size limit or payload cost disclosed in 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.

Conciseness4/5

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

Four sentences, front-loaded with the return shape before parameter and use-case detail. Mostly efficient, though the `map` instruction overlaps with what the schema already says, so it isn't maximally tight.

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?

A read-only tool with full annotation coverage and no output schema; the description explains return values and the two main usage modes. It is nearly complete, missing only edge details like the map size limit and how results are ordered/truncated.

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?

Schema coverage is 100% (baseline 3), and the schema already documents all five parameters exhaustively. The description goes slightly beyond by framing `planned` as a pre-build check against the Main Quest, but mostly restates the `map` parameter the schema already defines.

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 ('Returns') and resource ('flows in a feature map') and details what each returned flow contains: 'the screen, route, components and data files of every step.' An agent can tell this is the read counterpart to build-feature-map and update-feature-map without opening either schema.

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 usage context: unfiltered calls list every flow plus the Main Quest, and `planned` is for checking new work before building it. However, it never names the sibling alternatives (build-feature-map, update-feature-map) or states when NOT to use this read.

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

All Better Design toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources