Skip to main content
Glama

NASC: Networked AI Session Continuity

nasc_turn

Records one conversation turn for a registered direct-turn surface (Grok Bot) into the caller's own active session; it requires session_id and turn_id and follows organization capture policy. Scribe saves conversation turns, and other callers are refused.

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": {
      "role": "<role>",
      "content": "<content>"
    },
    "name": "nasc_turn"
  }
}

Input Schema

NameRequiredDescriptionDefault
whoNoOperator name label. Attribution comes from the authenticated account.
roleYes
brainNoOptional target org (brain uuid). Ignored unless this account can already access it; it never grants access.
contentYes
projectNoProject slug.
turn_idNoRequired stable native turn id; retries are idempotent.
session_idNoRequired session id from nasc_start.
source_platformNoPlatform the content came from.
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.3/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 and does disclose some important behavior: it writes into an active session, follows organization capture policy, and refuses other callers. However, it does not explain return behavior, error handling, ordering guarantees, or exactly what 'Scribe' means in this context.

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?

The description is two sentences and front-loads the core action and scope. The final clause about Scribe and refused callers is slightly cryptic but still relevant to access behavior.

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

Completeness2/5

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

This is a nine-parameter mutation tool with no annotations and no output schema, so the description must do more. It covers required IDs and access policy but omits return shape, failure modes, session-state assumptions, and how the many optional parameters interact.

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 high at 78%, so the schema documents most parameters. The description adds that session_id and turn_id are required, but it does not add meaning beyond the schema for the other seven parameters.

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 states a specific verb and resource: recording one conversation turn into the caller's active session for a registered direct-turn surface. It is distinguishable from session lifecycle tools like nasc_start, though it does not explicitly compare itself to any sibling.

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?

It implies usage for Grok Bot direct-turn surfaces and states that session_id and turn_id are required. It does not say when to prefer nasc_turn over alternatives or clarify what happens for non-registered callers beyond refusal.

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