Skip to main content
Glama

Server Details

A field manual for product and engineering leaders. Search it, or build its eight frameworks.

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A3.5/5.0

Scored across 30 tools

Disambiguation3/5

The eight *_apply_commands tools share nearly identical boilerplate descriptions and are distinguished only by the document type buried in a cryptic prefix (cfd, noice, ost, roi, usm, vsm), so an agent must first call tools_get_document to learn the tool key before it can pick the right write tool. The spaces_* tools are reasonably distinct from each other, as are the content tools, though search_collection vs lil_nerdy_ask_question both answer questions and must be told apart by description alone.

Naming Consistency3/5

There is a rough prefix_verb_noun convention (spaces_add_note, tools_get_document, ost_apply_commands), but prefixes are inconsistent — some are opaque builder codes (cfd, noice) while others are full words (roadmap, wardley), and tools_ is a meaningless catch-all namespace. The content tools (get_note, list_by_tag, search_collection) and lil_nerdy_ask_question drop the prefix entirely, so the set mixes several naming schemes.

Tool Count2/5

At 30 tools the surface is bloated, largely because eight near-identical apply_commands variants pad the count; those could plausibly collapse into one tool taking the document's tool key. Each individual group is coherent, but the total exceeds what an agent can comfortably scan for a mission that is mostly 'read content' plus 'edit my builder documents'.

Completeness3/5

Content browsing is well covered (search, get, by-category, by-tag, backlinks) and documents/spaces have create-read-export-share flows, but there are notable gaps: no delete or rename for documents, no delete/rename Space operation, and no way to change an existing member's role. History restore exists only indirectly via a RestoreTo command, which agents can work around but not discover from the tool list.

Available Tools

23 tools
get_noteFetch a note by slugA
Read-only
Inspect

Retrieve the full markdown body of a single note by its slug (e.g. "concepts/teaming/team-topologies"). Every published note is public.

Inputs: slug (required).

lil_nerdy_ask_questionAsk Lil NerdyA
Destructive
Inspect

Ask Lil Nerdy, Nerd/Noir's own assistant, and get its answer with the collection pages it drew on. Use it when the user asks for Lil Nerdy, or for Nerd/Noir's judgment on their situation; for a plain lookup, search the collection yourself. It knows the reader's saved memories, and for a reader with workshop access it can cite that workshop's slides. Each call is a new conversation: pass only the earlier turns with Lil Nerdy that the question depends on, as history. Pass document_id to ask about one of their builder documents; with edit allowed, it can change that document. Each call counts against the reader's chat allowance on nerdnoir.ai and can take 20 to 60 seconds.

Inputs: question (required), page, history, document_id.

list_by_categoryList notes by categoryA
Read-only
Inspect

Return all published notes in a given top-level category. Common categories: concepts, tools, resources, case-studies, sources, workshops.

Inputs: category (required).

list_by_tagList notes by tagA
Read-only
Inspect

List every published note that carries a tag, with its slug, title, category, and excerpt. Use it to gather the notes on one theme when a note from search_collection or get_note shows a tag worth following, for example "team-topologies". The match ignores case.

Inputs: tag (required).

search_collectionSearch the collection
Read-only
Inspect

Semantic search across the collection, the same engine as the chat on nerdnoir.ai. Returns the closest notes with slug, title, a short excerpt, and the page URL, best first. Optional filters narrow by frontmatter. For a signed-in reader with workshop access, results can include slides from those workshop decks (kind "slide"). Read a note in full with get_note. For Nerd/Noir's judgment on the reader's own situation, use lil_nerdy_ask_question instead.

Inputs: query (required), limit, filters.

spaces_add_noteAdd a page to a SpaceAInspect

Add a published page to the end of a Space. Needs the owner or editor role. Adding a page that is there already changes nothing.

Inputs: slug (required), spaceId (required).

spaces_create_spaceMake a SpaceAInspect

Make a shared Space owned by the user, optionally with its first notes in order. Names are unique per owner.

Inputs: name (required), slugs, description.

spaces_get_spaceRead one SpaceA
Read-only
Inspect

Return one Space with its notes in order, its documents (each with the url that opens it in its builder), and its members with their roles. Private lists the documents the user keeps outside every Space. A cohort Space also lists its people: the cohort's members, by name.

Inputs: spaceId (required).

spaces_invite_membersAdd people to a Space by emailAInspect

Add up to 20 people to a Space with one role: editor (adds and changes things) or viewer (reads). Any email address works. Somebody with no account gets an invite email; somebody with one joins at once. Needs the owner or editor role. Returns one answer per address.

Inputs: emails (required), spaceId (required), role, documentId.

spaces_leave_spaceLeave a SpaceA
Destructive
Inspect

Take the signed-in user out of a Space. Their documents in it pass to the Space owner. The owner cannot leave; they hand the Space over or delete it.

Inputs: spaceId (required).

spaces_list_spacesList the Spaces the user holds a role inA
Read-only
Inspect

Return the user's Spaces with each one's id, kind (private, shared, or cohort: the Space of a workshop cohort the user is in), the user's role (owner, editor, or viewer), and how many notes, documents, and members it holds. Private comes first and belongs to the user alone.

Inputs: no named parameters.

spaces_remove_memberTake someone out of a SpaceB
Destructive
Inspect

Remove a member from a Space. Owner only. The person's documents in the Space pass to the Space owner, so nothing leaves the Space.

Inputs: userId (required), spaceId (required).

spaces_remove_noteRemove a page from a SpaceA
Destructive
Inspect

Take a page out of a Space's list. The page stays published, and the Space keeps its other pages and documents. Use it when the reader asks to drop a page from a Space; spaces_get_space lists the slugs in it. Needs the owner or editor role.

Inputs: slug (required), spaceId (required).

spaces_share_documentPut a document in a SpaceAInspect

Put a document in a Space so everyone in it can open it. Editors and the owner can change it; viewers read it. Name an existing spaceId, or newSpaceName to make one. Only the document owner may do this, and only into a Space where they are owner or editor. A document is in one Space at most, so this moves it.

Inputs: documentId (required), spaceId, newSpaceName.

spaces_transfer_documentHand a document to another member of its SpaceA
Destructive
Inspect

Make another member of the document's Space the owner of the document. Use it when the reader asks to hand a document over, for example before they leave the Space. Only the current owner may do this, and the new owner must hold a role on the Space; a cohort reader does not count. Get the member's userId from spaces_get_space.

Inputs: documentId (required), newOwnerId (required).

spaces_unshare_documentTake a document out of its SpaceA
Destructive
Inspect

Take a document out of its Space, so it is personal to its owner again. Only the document owner may do this; the Space itself is left alone.

Inputs: documentId (required).

tools_apply_commandsChange a tool document
Destructive
Inspect

Change one document in any builder: roadmap (Outcome-Based Roadmap), roi (ROI Calculator), noice (NOICE Prioritization), ost (Opportunity Solution Tree), usm (User Story Map), vsm (Value Stream Map), cfd (Cumulative Flow Diagram), wardley (Wardley Map). Apply up to 25 commands as one atomic batch: all apply or none do. Read the document with tools_get_document first. It returns the toolKey to pass here, the version to pass as expectedVersion, and the commands that builder takes, each with its fields. A later command may name an entity an earlier one created only if you supplied no ids; read the result for the ids it assigned. StartOver clears a document, and RestoreTo with an event id from tools_get_history puts it back to that point. Send the same batchId again to retry safely after a timeout.

Inputs: toolKey (required), commands (required), documentId (required), expectedVersion (required), +1 more.

tools_create_documentCreate a tool documentAInspect

Create a new, empty document for the signed-in user in one of the builders. Returns the new id and version. Pass spaceId to start it inside a shared Space the user can edit; without it the document is personal. Pass idempotencyKey and a repeat of the same call returns the document it already made rather than a second one. Give the reader the returned url: it opens the document in its builder.

Inputs: toolKey (required), title, spaceId, idempotencyKey.

tools_export_documentExport a tool documentB
Read-only
Inspect

Export a document as a file. format "json" (the default) returns the snapshot the builder's Download JSON writes: the saved state, which the Scenarios Upload button imports as a new document, a summary, and the canonical entities (outcomes, with their kind, metrics, and bets) in one vocabulary across tools. format "markdown" returns the document as markdown.

Inputs: documentId (required), format.

tools_get_documentRead a tool document
Read-only
Inspect

Return a document: its toolKey, title, version, url (the page that opens it in its builder), the current state as a projection with real ids, and the commands that tool takes, each with its fields. Read this before you change anything, then write with tools_apply_commands: pass its toolKey, and its version as expectedVersion.

Inputs: documentId (required).

tools_get_historyRead the recent history of a tool documentA
Read-only
Inspect

Return the most recent events on a document, newest first, each with its event id and a plain description. Use an event id with a RestoreTo command to put the document back to the state right after that event.

Inputs: documentId (required), limit.

tools_list_documentsList the documents the user can reachA
Read-only
Inspect

Return the tool documents the signed-in user owns or shares through a Space, most recently edited first, with each one's id, tool, version, role, Space, and url (the page that opens it in its builder). Pass toolKey to list one builder's documents. Every other document tool needs one of these ids.

Inputs: toolKey.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources