GenFlick

activate toolset

native.activate_toolset

DestructiveIdempotent

Load an exact pack id from the capabilities directory (no functions. prefix) with its skill. A pack marked loaded or listed in activeToolsets is already active: never load it again. Batch anticipated missing packs with independent reads and actions; newly loaded tools are usable on the next model turn.

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": {
      "work_id": "<work_id>",
      "arguments": "<arguments>",
      "expected_catalog_version": "<expected_catalog_version>",
      "read_skills": "<read_skills>",
      "request_key": "<request_key>"
    },
    "name": "native.activate_toolset"
  }
}

Input Schema

Name	Required	Description
`work_id`	Yes
`arguments`	Yes
`read_skills`	Yes	Exact required native skills and their dependencies, copied from the accepted session bootstrap's skills array. Include only entries in that array. General mcp.* guides and native.{studio}.instructions are guidance, not native skill proofs.
`request_key`	Yes
`publication_proposal_id`	No	For native Social scheduling, the exact server-approved publication proposal. This identifier cannot confer approval by itself.
`expected_catalog_version`	Yes	For a new session, read a studios/{studio}/native/{pack} child toolset and copy invocation.catalog_version from a native tool descriptor. Do not use the top-level library version. For calls in an existing session, use that session proposal's catalog_version.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Adds real behavior beyond annotations: newly loaded tools only become usable on the next model turn (a latency/turn-boundary constraint) and packs already loaded must not be re-loaded. It does not explain why destructiveHint=true applies to a load operation, nor any permission or failure-mode behavior.

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 tightly packed sentences with the core action and the re-load prohibition front-loaded. The batching sentence is telegraphic ('independent reads and actions') and borders on ambiguous, but nothing is redundant.

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 six-parameter state-changing meta tool with an output schema, the description covers the critical decision points: correct id format, do-not-reload rule, batching, and turn-boundary availability. Gaps remain around permissions and the reason for the destructive hint, but nothing blocks a correct invocation.

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 50%. The description clarifies the key argument (toolset_id is a pack id, unprefixed) but says only 'with its skill' about read_skills and never mentions work_id, request_key, or the catalog-version/proposal-id requirements that the schema documents instead. Baseline 3 fits since the schema carries much of the load.

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: load an exact pack id from the capabilities directory, including the 'no functions. prefix' qualifier. It is distinguishable from siblings like native.discover_capabilities or get_toolset by its load-vs-look-up effect, though it never names those siblings explicitly.

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?

Explicitly gives a when-not-to-use rule ('a pack marked loaded or listed in activeToolsets is already active: never load it again') and advises batching anticipated missing packs. It stops short of naming the discovery/sibling tools an agent should call first to find pack ids.

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

All GenFlick tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?