Skip to main content
Glama
Sign In
Unilytics MCP Server

Unilytics MCP Server

Official
by TeamUnilytics
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

add_skill_to_folder

Idempotent

Attach a skill to a folder by reference so its files stay in the skill store; this records the folder-skill link without copying files, and repeated attaches change nothing.

Instructions

Attach a skill to a folder by reference (the skill's files stay in the skill store).

Records that the folder contains the skill; the skill's files aren't copied. A repeat with the
same skill changes nothing.

Args:
    folder_id: The folder ID (from list_folders or create_folder).
    skill_id: The skill ID to attach.

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": {
      "folder_id": "<folder_id>",
      "skill_id": "<skill_id>"
    },
    "name": "add_skill_to_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
skill_idYes
folder_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.0
    • removedInput schema / properties / config
      Removed value: -{
-  "default": null,
-  "title": "config",
-  "type": "string"
-}
  2. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=true, so the description's main added value is the reference-vs-copy semantics: the folder merely records containment and the skill's files are not duplicated. That is real behavioral context an agent cannot get from the annotations. Gaps remain around failure modes (missing folder or skill) and any permission requirements.

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?

The core behavior is front-loaded in the first sentence and the Args block is compact. The copy semantics are stated twice ('stay in the skill store' and 'aren't copied'), which is mild redundancy but reinforces the key point rather than bloating the text.

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 two-parameter mutation with annotations covering safety and idempotency and no output schema, the description supplies enough to invoke it correctly. It omits error behavior and the source of skill_id, which would be nice but are minor for a tool this simple.

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 0%, so the description carries the burden, and it does define both parameters in the Args block, including where folder_id comes from. However, it adds no format details and says nothing about the origin or validation of skill_id, so the compensation is only partial.

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 a specific verb and resource ('Attach a skill to a folder') and immediately qualifies the operation as 'by reference', which separates it from copy/upload-style siblings like upload_file_to_project. The parenthetical that files stay in the skill store makes the effect unambiguous, though no sibling is named explicitly.

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?

Usage context is implied rather than stated: the folder_id provenance note ('from list_folders or create_folder') hints at the call sequence, and the idempotency sentence tells the agent repeat calls are safe. There is no explicit when-to-use vs. when-not guidance and no mention of an alternative for actually copying files.

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