Skip to main content
Glama

NASC: Networked AI Session Continuity

nasc_route

Files the current conversation under a project: the signal renders in the conversation and the NASC web-capture extension files the chat. The orphaned holding pen is rejected.

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": {
      "project": "<project>"
    },
    "name": "nasc_route"
  }
}

Input Schema

NameRequiredDescriptionDefault
brainNoOptional target org (brain uuid). Ignored unless this account can already access it; it never grants access.
projectYesProject slug.
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

C2.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose real behavior beyond the schema: the signal is rendered into the conversation and an external web-capture extension files the chat, plus a rejection rule for orphaned state. It omits permission/auth requirements, whether the filing is idempotent or overwrites prior routing, and what the agent observes on success versus rejection.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but the second sentence is dense internal jargon ('the signal renders', 'web-capture extension', 'orphaned holding pen') that does not clearly earn its place. The core action is front-loaded, but the trailing clauses reduce rather than increase comprehension.

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 four-parameter mutation with full schema coverage and no output schema, the definition is marginally adequate: it covers the main action and some side effects. It still leaves out what happens on failure, what the rendered signal looks like, and how session pinning interacts with the project argument.

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 100%, so baseline is 3. The description only reinforces that the operation targets a project, adding no meaning about brain, session_id, or continuity_token beyond what the schema already states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening clause gives a concrete verb+resource: 'Files the current conversation under a project.' But the remainder ('the signal renders in the conversation and the NASC web-capture extension files the chat') describes side effects rather than the core action, and 'The orphaned holding pen is rejected' is unexplained jargon. An agent can guess the gist but not cleanly distinguish this from siblings like nasc_turn or nasc_session_cleanup.

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

Usage Guidelines2/5

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

No explicit when-to-use or when-not-to-use guidance is given, and no alternatives are named. The only contextual hint is an unexplained precondition ('the orphaned holding pen is rejected'), which does not tell an agent when to choose nasc_route over nasc_turn, nasc_start, or nasc_intake.

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