Skip to main content
Glama

create_now_assist_skill

Creates a draft Now Assist skill from input/output schemas and a prompt template, plus its config registration, so you can finish and activate it in Now Assist Skill Kit.

Instructions

Create a draft Now Assist skill: a OneExtend capability (type skill, holding the input/output schema and prompt template in its metadata) plus its sn_nowassist_skill_config registration. Finish the prompt/provider in Now Assist Skill Kit before activating (requires NOW_ASSIST_ENABLED + WRITE_ENABLED)

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": {
      "name": "<name>",
      "description": "<description>",
      "input_schema": "<input_schema>",
      "output_schema": "<output_schema>",
      "prompt_template": "<prompt_template>"
    },
    "name": "create_now_assist_skill"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesSkill name
modelNoOptional model identifier to use for this skill
activeNoActivate the skill config right away (default false: finish the prompt and provider in Now Assist Skill Kit first)
descriptionYesSkill description
input_schemaYesJSON schema string defining the skill input
skill_familyNoOptional Now Assist skill family (sys_id or name, default "Platform")
output_schemaYesJSON schema string defining the skill output
prompt_templateYesPrompt template for the skill

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv5.0.1
    • addedInput schema / properties / active
      Added value: +{
      +  "description": "Activate the skill config right away (default false: finish the prompt and provider in Now Assist Skill Kit first)",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / skill_family
      Added value: +{
      +  "description": "Optional Now Assist skill family (sys_id or name, default \"Platform\")",
      +  "type": "string"
      +}
  2. Addedv4.9.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare non-readonly, non-idempotent, open-world, non-destructive, which is thin for a two-record creation. The description adds real substance: two artifacts are written, the skill is created inactive by default, and two feature flags must be enabled. It stops short of covering duplicate-name handling or what happens if the config registration fails after the capability is written.

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?

Front-loaded with the core action and artifact list, then the operational caveat and prerequisites in a compact parenthetical. Dense with domain jargon but every clause carries information; no filler sentences.

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 an 8-parameter, 5-required creation tool with no output schema and no nested objects, the description covers what gets created, the draft state, and environment requirements. The notable gap is the return value — an agent does not learn whether it receives the created sys_ids or just a status — which matters since there is no output schema to consult.

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 100%, so every parameter is already documented, and the description mostly reinforces rather than extends that. It does clarify the 'active' semantics (default false, finish prompt and provider first), but adds nothing about skill_family defaults, model selection, or expected JSON schema string formats beyond what the schema states.

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?

Names a specific verb and resource (create a draft Now Assist skill) and goes further by naming the two underlying artifacts it produces: a OneExtend capability of type 'skill' and its sn_nowassist_skill_config registration. That level of specificity distinguishes it from get_now_assist_skill, test_now_assist_skill, and list_now_assist_skills without needing to inspect schemas.

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?

States the operating context and prerequisites clearly: the result is a draft, the prompt/provider must be finished in Now Assist Skill Kit before activation, and the environment requires NOW_ASSIST_ENABLED plus WRITE_ENABLED. It does not explicitly route the agent between this tool and siblings like test_now_assist_skill, but the draft-then-finish workflow makes the intended position in the sequence evident.

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

Deploy Server

Other Tools