Skip to main content
Glama

test_now_assist_skill

Test a Now Assist skill with sample input to verify behavior before use; requires NOW_ASSIST_ENABLED.

Instructions

Invoke a Now Assist skill with test input to verify behavior (requires NOW_ASSIST_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": {
      "skill_sys_id": "<skill_sys_id>",
      "test_input": "<test_input>"
    },
    "name": "test_now_assist_skill"
  }
}

Input Schema

NameRequiredDescriptionDefault
asyncNoRun as a background job and return a job_id at once. Poll it with get_job. Calls that take longer than about 20 seconds switch to a job on their own.
test_inputYesTest input payload to send to the skill
skill_sys_idYesSystem ID of the skill to test

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv5.0.1
    • addedInput schema / properties / async
      Added value: +{
      +  "description": "Run as a background job and return a job_id at once. Poll it with get_job. Calls that take longer than about 20 seconds switch to a job on their own.",
      +  "type": "boolean"
      +}
  2. Addedv4.9.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true, so the safety profile is largely covered. The description contributes the feature-flag prerequisite, which is real added context, but it does not address whether invoking a skill with test input actually executes side effects against the skill or is a sandboxed dry run — a meaningful question given readOnlyHint=false.

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?

A single front-loaded sentence with no filler; the action and the prerequisite are stated before any caveat. It is efficient, though the parenthetical prerequisite could be more prominent than a trailing clause.

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

Completeness3/5

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

There is no output schema, so the description should say what a test invocation returns (pass/fail, logs, records), especially since the async path returns a job_id instead. For a tool taking a free-form nested test_input object, the definition also omits any hint about expected payload structure.

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%, and the async parameter's schema text already covers job fallback and polling via get_job, so the structured data does the heavy lifting. The description adds no meaning beyond the schema for skill_sys_id or the nested test_input payload shape.

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?

States a specific verb and resource ('Invoke a Now Assist skill') plus the intent ('with test input to verify behavior'), which clearly separates it from create_now_assist_skill, get_now_assist_skill, and list_now_assist_skills. It stops short of naming near-neighbor test tools like test_flow or run_atf_test, so the differentiation is implicit rather than explicit.

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?

The parenthetical '(requires NOW_ASSIST_ENABLED)' gives a concrete prerequisite, which is genuine usage guidance. However, there is no statement of when to prefer this over sibling test tools (test_flow, test_agent_access, run_atf_test) or when not to use it, leaving selection to inference.

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