Skip to main content
Glama

NASC: Networked AI Session Continuity

nasc_assets

Project assets registry. register upserts one (requires asset_name, asset_type); query searches; update changes one (requires asset_name or asset_id).

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

Input Schema

NameRequiredDescriptionDefault
brainNoOptional target org (brain uuid). Ignored unless this account can already access it; it never grants access.
notesNo
actionYes
searchNo
projectNoProject slug.
add_linkNo
asset_idNo
asset_nameNo
asset_typeNo
blocked_byNo
session_idNoOptional session id from nasc_start. Pins this call's authorization, org and project to that session.
build_stateNo
descriptionNo
dependenciesNo
include_linksNo
related_filesNo
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.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. 'Register upserts' is a genuinely useful disclosure that the schema does not convey, but for a mutating tool with 17 parameters there is no mention of permission requirements, what update overwrites or destroys, or how conflicts/duplicates are resolved.

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?

Three compact clauses, front-loaded with the resource and then action-by-action; every sentence carries content and nothing is padded. The density is arguably too high given how much it leaves out, but on conciseness and ordering it is well built.

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?

Given 17 parameters, a nested add_link object, no annotations and no output schema, this one-line description is far too thin. An agent still cannot tell what query returns, what fields update accepts, or what the session/brain scoping implies for authorization beyond what the schema properties themselves state.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 24% across 17 parameters, most of which (search, notes, include_links, build_state, dependencies, related_files, add_link, blocked_by) are undocumented anywhere. The description clarifies only asset_name, asset_type and asset_id requirements, leaving the majority of parameters semantically opaque.

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 assets registry') and disambiguates the three action modes: register upserts, query searches, update changes. An agent can tell what the tool operates on and which mode performs which verb, though it never contrasts itself against siblings like nasc_docs or nasc_wiki that might also hold artifact-like records.

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 gives per-action requirements ('register ... requires asset_name, asset_type', 'update ... requires asset_name or asset_id'), which is real guidance for picking an action. It says nothing about when to use this registry versus the sibling tools, nor about prerequisites or ordering constraints.

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