Skip to main content
Glama

NASC: Networked AI Session Continuity

nasc_projects

Project registry. list returns real projects. register creates one (requires slug and name). list_orphaned lists capture sessions in the orphaned holding pen. adopt moves an orphaned session and its chunks into a real project (requires session_id and project).

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": {
      "action": "<action>"
    },
    "name": "nasc_projects"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgNoOptional org (brain uuid) to register into without switching the active brain; requires owner membership or platform super-admin. brain instead switches the whole call.
nameNoregister: display name.
slugNoregister: unique id of lowercase letters and digits joined by single hyphens, dots or underscores, max 64 characters ('orphaned' is reserved).
brainNoOptional target org (brain uuid). Ignored unless this account can already access it; it never grants access.
actionYes
projectNoadopt: target real project slug, never orphaned or a system project.
metadataNoregister: optional.
session_idNolist/register: current root session, as authorization context only. adopt: the orphaned session to move.
descriptionNoregister: optional one line.
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

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the key mutation semantics — register creates a project, adopt moves a session and its chunks into a real project — which is the most important behavioral fact. However it says nothing about permissions, whether adopt is reversible, what happens to the orphaned holding pen entry afterwards, or error conditions, leaving real gaps for a write-capable tool.

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?

Four short sentences, one per action, front-loaded with the resource identity and then ordered by action. Every clause carries information; there is no filler or restatement of the tool name.

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?

For a 10-parameter, four-action tool with no annotations and no output schema, the description covers the action semantics and the conditional required parameters well. It leaves the authorization/org-switching behavior (org vs brain vs continuity_token) entirely to the schema and gives no sense of what list or list_orphaned return, which matters since there is no output schema.

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 90%, so the baseline is 3, but the description adds genuinely non-redundant information: the schema marks only 'action' as required, while the description states that register requires slug and name and adopt requires session_id and project. That conditional-requirement mapping is exactly the kind of meaning the schema does not encode. It does not touch org, brain, continuity_token, metadata or description, which the schema already documents.

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 names the resource ('Project registry') and then gives a distinct verb+object for each of the four actions: list returns real projects, register creates one, list_orphaned lists capture sessions in the holding pen, adopt moves an orphaned session and its chunks. An agent can map each enum value to a concrete operation without opening the schema. It stops short of 5 because it never contrasts itself with the surrounding nasc_* tools or states the boundary of the registry concept.

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 implied rather than stated: adopt is clearly the follow-up to list_orphaned, and list is the default read. But there is no explicit when-to-use/when-not guidance, no statement of prerequisites (e.g. that adopt only applies to sessions surfaced by list_orphaned), and no mention of when to prefer register over other project-creation paths.

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