Skip to main content
Glama

NASC: Networked AI Session Continuity

nasc_docs

Documents: AI-authored work product (specs, drafts, notes), unlike the wiki, which the AI cannot write. create writes one; get opens one by id; update changes provided fields of a draft or active doc; list returns stubs, newest first. Docs also appear in search. Retiring a doc belongs to the triage tool.

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_docs"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoDoc uuid; required for get and update.
whoNoOperator name label. Attribution comes from the authenticated account.
bodyNoMarkdown, required on create. Max 512KB.
tagsNoOptional tags.
brainNoOptional target org (brain uuid). Ignored unless this account can already access it; it never grants access.
limitNolist: 1-50, default 20.
titleNoRequired on create. Max 400 chars.
actionYes
formatNoOnly markdown is accepted.
statusNoDefault active on create.
projectNoProject 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

A4.4/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 disclosure burden. It usefully discloses that list returns stubs newest-first, that update only changes provided fields, and that retiring belongs elsewhere, but omits permissions/auth expectations, whether updates are reversible, and what get returns beyond 'opens one'.

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 compact sentences, each carrying a distinct fact: identity vs wiki, per-action behavior, search visibility, and the triage handoff for retirement. The resource identity and the create/get/update/list breakdown are front-loaded with zero filler.

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

Completeness4/5

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

For a 13-parameter tool with no annotations and no output schema, the description covers the action semantics and sibling routing well. Remaining gaps are return-shape detail for get/list and the session/continuity pinning parameters, most of which the schema already explains.

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 92%, so the schema already documents most parameters (id, body, title, brain, limit, status). The description adds routing meaning by tying id to get/update and describing list's ordering and stub output, though it adds nothing on session_id or continuity_token.

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 names the concrete resource (AI-authored docs: specs, drafts, notes), lists the four actions with their individual behaviors, and explicitly distinguishes it from the wiki sibling. An agent can identify what the tool does and how each action behaves without opening the schema.

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 when to use this over the wiki (the AI cannot write the wiki), routes doc retirement to nasc_triage, and notes docs are also reachable via search. Both an alternative and an exclusion are given, leaving little to infer.

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