Skip to main content
Glama

nexo_artifact_create

Register a new artifact (service, dashboard, script, API, etc.) in the Artifact Registry for discovery and management.

Instructions

Register a new artifact (service, dashboard, script, API, etc.) in the Artifact Registry. Call this whenever NEXO creates, deploys, or discovers a runnable/accessible artifact.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindYesType — service, dashboard, script, api, cron, website, database, repo, config, tool, plugin, other
canonical_nameYesPrimary name (e.g., 'NEXO Brain Dashboard')
aliasesNoJSON array of alternative names users might use (e.g., '["backend", "dashboard", "nexo web"]')[]
descriptionNoWhat it does (1-2 sentences)
uriNoAccess URL or address (e.g., 'localhost:6174', 'nexo-brain.com')
portsNoJSON array of ports (e.g., '[6174]')[]
pathsNoJSON array of file paths (e.g., '["/Users/x/nexo/src/dashboard/app.py"]')[]
run_cmdNoCommand to start/open it (e.g., 'python3 -m dashboard.app --port 6174')
repoNoRepository path or URL
domainNoProject domain (nexo, my-project, project-a, project-b, etc.)
session_idNoCurrent session ID
metadataNoJSON object with extra key-value pairs{}
forceNoSet to '1'/'true' to bypass Fase 2 R09 dedup when the duplicate is intentional (e.g. re-registering after archive). Without force, any match on canonical_name+domain / uri / port / path returns an error pointing at the existing artifact.
Behavior2/5

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

No annotations provided, so description carries full burden. It does not disclose side effects, authorization needs, or dedup behavior (force param not mentioned). Significant gaps.

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?

Two sentences, front-loaded with purpose and examples. No wasted words.

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 13 parameters, no output schema, no annotations, the description is too minimal. Missing info on return value, error handling, and force usage.

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 100%, so baseline is 3. Description adds no additional parameter info beyond the schema. Adequate but no extra value.

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 clearly states the verb (Register) and the resource (artifact) with examples, and it helps distinguish from siblings like delete/find/list/update. However, it does not explicitly differentiate when to use this over update.

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?

Provides clear usage context: 'Call this whenever NEXO creates, deploys, or discovers a runnable/accessible artifact.' Lacks exclusions or alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wazionapps/nexo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server