Skip to main content
Glama

Inspect Workspace & Database Health Status

nomos_status
Read-onlyIdempotent

Returns workspace lifecycle phase, active Git branch, SQLite ledger health, and aggregate task counts to check host/database readiness or current branch state.

Instructions

Return a concise snapshot of workspace lifecycle phase, active Git branch, SQLite ledger health, and aggregate task counts. Use when checking overall host/database readiness or current branch state. Do NOT use when requesting full JIT phase playbooks (use nomos_handshake instead) or scanning code debt (use nomos_xray instead).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nomos_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
phaseNoCurrent workspace lifecycle phase.
branchNoCurrent Git branch name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so safety is fully covered structurally. The description adds value beyond that by disclosing the actual content inventory of the snapshot (ledger health, branch, task aggregates), though it says nothing about freshness or cost of the call.

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?

Three tight sentences: what it returns first, then when to use, then when not to. Every sentence earns its place with no redundant restatement of the title.

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?

An output schema exists, so return-value detail is unnecessary, and annotations cover the safety profile. For a zero-parameter read-only status tool, the description supplies everything an agent needs to select and invoke it correctly.

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?

The tool takes zero parameters, so the schema carries no semantic burden and the baseline is 4. The description correctly implies a no-argument invocation by describing a passive inspection of ambient host state.

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?

The description opens with a specific verb and enumerates exactly what the snapshot contains: lifecycle phase, active Git branch, SQLite ledger health, and aggregate task counts. This makes it immediately distinguishable from siblings like nomos_xray (code debt) and nomos_handshake (phase playbooks).

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?

It states the positive trigger (checking host/database readiness or current branch state) and gives explicit exclusions with named alternatives for each: nomos_handshake for JIT phase playbooks, nomos_xray for code-debt scanning. The agent has no routing ambiguity left.

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