action,
target, or event parameter instead of one tool per verb. Every tool name
and action value on this page is read directly from the server’s tool
registry — see Usage for how that’s kept honest.
Quality scanners — scan
scan(target, directory, ...)
One dispatcher tool, 12 targets.
health is the primary entry point — runs
every scanner and can trigger remediation.
Pass
mode="migration" with target="health" to activate migration-intent
detection. Pass diff_scope=true/false to force diff-only or whole-repo
scope on health/security/full_suite (auto-resolved from story context
when omitted).
Remediation — remediate
remediate(action, ...)
Turns a
scan report into an autonomous or approved fix plan. Workflow orchestration — workflow
workflow(action, story_id, ...)
The SDLC state machine: init a story, advance phases, run parallel gates, merge back.
override=true on validate_and_advance forces a non-adjacent phase jump
(logs an L2 escalation; never bypasses artifact/blocker checks).
Validation — validate
validate(role, artifact_id, artifact_path)
Runs one role’s structural validator against its artifact and returns a JSON ValidationReport.
Agent control — agent
agent(action, name, ...)
List, activate, identify, or gate-check a persona.
force=true on activate bypasses the artifact-prerequisites gate (logs an
escalation). story_id on activate/check gates against a specific story
instead of the session’s active-story pointer.
Session context & knowledge graph — context
context(action, ...)
Session-scoped notes plus a queryable knowledge graph of the codebase and story history.
manage_context(action, ...) is a lighter standalone tool exposing only the
add/get/clear behavior above, for callers that don’t need the graph.
Pattern memory — pattern
pattern(action, ...)
Capture and reuse team conventions discovered while working a story.
Story sequencing — story
story(action, directory)
Cross-story dependency analysis, independent of any single story’s workflow state.
Browser / E2E testing — browser
browser(action, ...)
nablr cannot drive a browser itself — it hands out one conceptual test
step at a time; the calling agent runs it via its own Playwright MCP tools
and reports the real outcome back.
Requirements hierarchy — create_story / create_epic / create_feature
create_story / create_epic / create_feature
Write requirement docs the sanctioned way — never with a raw file write.
Codebase mapping & discovery
Discovery artifacts
Auto-document structure, features, agents, and requirements status.
Reporting
Quality gate & blockers
Session & story context
License tools
License tools
Trial activation, key management — always free, never gated.
Usage
Tools are available automatically once nablr is connected. Invoke them naturally:nablr.server.mcp.list_tools()) — if a tool is
renamed or an action added or removed, the check fails until this page is
updated to match.