Skip to main content
Glama

NASC: Networked AI Session Continuity

nasc_start_status

Reads the session and capture status of a nasc_start start_id and brain. It never starts a session. Capture attachment and the first saved turn have separate receipts.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "start_id": "<start_id>",
      "brain": "<brain>"
    },
    "name": "nasc_start_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
brainYesOptional target org (brain uuid). Ignored unless this account can already access it; it never grants access.
start_idYes
session_idNoOptional session id from nasc_start. Pins this call's authorization, org and project to that session.
continuity_tokenNoOptional host conversation id. Resolves the active session and pins this call's authorization, org and project to it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It does valuable work by declaring the operation read-only in plain language ('Reads', 'never starts a session') and by flagging that capture attachment and the first saved turn 'have separate receipts,' which warns the agent against expecting those results here. It says nothing about authorization requirements, latency/consistency timing, or what the status values can be, which is a real gap for an unannotated tool.

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?

Three short sentences, front-loaded with the core purpose and followed by the negative constraint and the receipt caveat. Nothing is redundant, though the final sentence is terse enough to be slightly cryptic without further context.

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

Completeness3/5

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

With no output schema, no annotations, and four parameters, the description should say more about what a status response contains and what the agent should do with it. It covers identity, read-only-ness, and the receipt caveat, but leaves return shape, error conditions, and authorization behavior undiscussed.

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

Parameters3/5

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

Schema description coverage is 75%, so the schema already explains brain, session_id, and continuity_token fairly well. The description only reinforces that start_id and brain are the identifying pair and adds no syntax or format detail; the two optional parameters that pin authorization, org, and project are left entirely to the schema.

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?

The description uses a specific verb and resource ('Reads the session and capture status') and names the exact inputs that identify the record ('a nasc_start start_id and brain'). It also draws a line against the sibling nasc_start ('It never starts a session'), so an agent can tell it apart from the operation that creates a session, though the term 'capture status' is left undefined.

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

Usage Guidelines3/5

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

Usage is only implied: by saying it 'never starts a session,' the reader infers that session creation belongs to nasc_start and this tool is for checking on it afterwards. There is no explicit statement of when to call this versus nasc_session_cleanup, nasc_live, or nasc_turn, and no preconditions or failure conditions are given.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources