Skip to main content
Glama

NASC: Networked AI Session Continuity

nasc_wiki

Interlinked knowledge wiki with bounded, traverse-style retrieval. find returns page stubs; get opens one page with its links and backlinks (project is OPTIONAL for get: a globally unique slug resolves across visible projects, and a slug in 2+ projects returns { found:false, ambiguous:true, candidates:[{slug,project,title}] }); links returns a page's graph neighborhood; list indexes pages by kind; audit reports redlinks, orphans, unreachable nodes, lean-policy violations and verb coverage. Synthesis writes pages and people edit them in the Control Panel; this tool has no write action, and the triage tool retires stale pages.

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

Input Schema

NameRequiredDescriptionDefault
whoNoOperator name label. Attribution comes from the authenticated account.
kindNofind/list filter.
slugNoPage slug, the [[link]] target (get/links).
brainNoOptional target org (brain uuid). Ignored unless this account can already access it; it never grants access.
queryNofind: natural-language query.
actionYes
projectNoProject slug.
session_idNoOptional session id from nasc_start. Pins this call's authorization, org and project to that session.
match_countNofind: 1-25, default 8.
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.1/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it declares the tool read-only, discloses the ambiguous-slug response shape ({found:false, ambiguous:true, candidates:[...]}), and characterizes retrieval as bounded/traverse-style. It does not state result caps or pagination for find/links beyond the match_count schema hint, which keeps it short of a 5.

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?

Information-dense and front-loaded: the one-line framing comes first, then a compact per-action enumeration, then the write/retire boundary. It is a single long paragraph rather than a list, but almost every clause carries distinct content and none is padding.

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 10-parameter, five-action tool with no output schema, the description covers the action set, the shape of get's result, and the ambiguity edge case, which is what an agent most needs. Return shapes for find, list, and audit are left implicit, though the schema's 90% coverage offsets much of that.

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 coverage is 90%, so the schema already documents nearly every parameter and the baseline is 3. The description does add real meaning beyond it for the project parameter (optional on get, global slug resolution across visible projects, ambiguity behavior), but that is the only parameter it enriches.

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 a specific resource (an interlinked knowledge wiki) and then defines each of the five actions distinctly: find returns stubs, get opens one page with links and backlinks, links returns the graph neighborhood, list indexes by kind, audit reports redlinks/orphans/lean-policy violations. An agent can tell exactly what each action does 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 Guidelines4/5

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

It gives explicit negative guidance ('this tool has no write action') and routes writes to the Control Panel and stale-page retirement to nasc_triage, plus clarifies that get works without a project slug. It does not distinguish this wiki retrieval from the sibling nasc_search, so the boundary with a general search tool is left to inference.

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