Skip to main content
Glama
Sign In

uCoz

by io.github.ucoz-skills
OverviewDiscussionsAdmin

uCoz agent skills

skills_tool

Looks up official uCoz agent skills. resolve matches a skill to a task description, catalog lists available skills, register_usage records skill usage for the selected site (requires select_site).

Input Schema

NameRequiredDescriptionDefault
refNoGit branch or tag. Default: main.
repoNoGitHub repo with skills. Default: ucoz-skills/agent-skills.
taskNoresolve: user task wording (the first 2000 characters are matched).
limitNoresolve: how many matching skills to return, the primary one included (default 3, up to the whole catalog).
scopeNoinstall/status paths: global (~/.cursor/skills) or project (workspace/.cursor/skills). Default global.
actionYesresolve — match skill by task. catalog — GitHub list. status — check_paths of a skill installation. install — source and target location of a skill. register_usage — site usage tracking (select_site); best effort: recorded=false with a message when tracking is temporarily unavailable.
clientNoIDE client for status/install paths (default auto → cursor).
compareNostatus: include catalog latest_version.
versionNoregister_usage: skill version (synonym skill_version).
skill_idNoSlug (^[a-z0-9-]+$). Required for install; optional for catalog/status/register_usage.
skill_pathNoregister_usage: path to SKILL.md (alternative to skill_id + version).
skill_versionNoSynonym for version (register_usage).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"resolve: max alternatives (1–7, default 3)."New value: +"resolve: how many matching skills to return, the primary one included (default 3, up to the whole catalog)."
    • changedInput schema / properties / task / description
      Previous value: -"resolve: user task wording."New value: +"resolve: user task wording (the first 2000 characters are matched)."
  2. Changed1 schema field changed
    • changedInput schema / properties / action / description
      Previous value: -"resolve — match skill by task. catalog — GitHub list. status — check_paths of a skill installation. install — source and target location of a skill. register_usage — site usage tracking (select_site)."New value: +"resolve — match skill by task. catalog — GitHub list. status — check_paths of a skill installation. install — source and target location of a skill. register_usage — site usage tracking (select_site); best effort: recorded=false with a message when tracking is temporarily unavailable."
  3. Changed5 schema fields changed
    • changedInput schema / properties / action / description
      Previous value: -"resolve — match skill by task. catalog — GitHub list. status — local check_paths (host agent verifies). install — install_command for host agent. register_usage — site usage tracking (select_site)."New value: +"resolve — match skill by task. catalog — GitHub list. status — check_paths of a skill installation. install — source and target location of a skill. register_usage — site usage tracking (select_site)."
    • changedInput schema / properties / client / description
      Previous value: -"IDE client for status/install path hints (default auto → cursor)."New value: +"IDE client for status/install paths (default auto → cursor)."
    • changedInput schema / properties / compare / description
      Previous value: -"status: include catalog latest_version for update hints."New value: +"status: include catalog latest_version."
    • removedInput schema / properties / method
      Removed value: -{
-  "description": "install: npx skills add (recommended) or git sparse copy hint.",
-  "enum": [
-    "auto",
-    "npx",
-    "copy"
-  ],
-  "type": "string"
-}
    • changedInput schema / properties / skill_path / description
      Previous value: -"register_usage only on host: path to SKILL.md (account MCP: prefer skill_id + version)."New value: +"register_usage: path to SKILL.md (alternative to skill_id + version)."
  4. First observed

TDQS

B3.1/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false and openWorldHint=true, meaning the agent knows writes/network are involved, but the description never explains that 'install' writes skill files into a filesystem path, what status inspects, or that behavior depends on a remote GitHub repo. The only added context is the select_site prerequisite and the best-effort tracking note (which is already duplicated from the schema). For a multi-mode tool with two unmentioned mutating actions, this is thin.

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 tight sentence with the primary purpose front-loaded and zero filler. It loses a point only because compression came at the cost of omitting two of the five actions rather than being deliberately scoped.

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?

With 12 parameters, 5 enum-gated actions, and no output schema, the description should explain each mode. It covers only resolve/catalog/register_usage, leaving status and install (the mutating one) entirely unexplained, so an agent cannot confidently select or invoke those modes from the definition alone.

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 in the input schema, including action, scope, client, and skill_id semantics. The description adds nothing beyond that (no mention of repo/ref defaults or limit behavior), so the baseline 3 applies.

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 ('Looks up official uCoz agent skills') and enumerates three actions, which distinguishes it clearly from the CRUD siblings. However, the schema exposes five actions (resolve, catalog, status, install, register_usage) while the description names only three, so the stated purpose under-describes the tool's actual surface.

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?

It gives partial routing cues ('resolve matches a skill to a task description, catalog lists available skills') and one hard prerequisite ('register_usage ... requires select_site'). But there is no guidance on when to choose status vs install, no mention of when this tool should be preferred over docs_tool, and no exclusions.

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

All uCoz toolsInspect
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