Skip to main content
Glama

humanMCP — kapoost

by io.github.kapoost

upsert_skill

Create or replace a skill by slug. Owner-only: requires Authorization: Bearer . Writes JSON to content/skills/.json.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYes
slugYes
tagsNo
titleYes
categoryYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • removedInput schema / properties / body / description
      Removed value: -"Markdown instructions"
    • removedInput schema / properties / tags / description
      Removed value: -"Optional group tags (e.g. [humanmcp, dev, safety]) for load_skill_group filtering."
  2. Changed1 schema field changed
    • addedInput schema / properties / tags
      Added value: +{
+  "description": "Optional group tags (e.g. [humanmcp, dev, safety]) for load_skill_group filtering.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
  3. Changed5 schema fields changed
    • removedInput schema / properties / category / description
      Removed value: -"Skill category (e.g. tech, writing, workflow)"
    • removedInput schema / properties / slug / description
      Removed value: -"Unique skill identifier"
    • removedInput schema / properties / tags
      Removed value: -{
-  "description": "Optional tags for filtering",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}
    • removedInput schema / properties / title / description
      Removed value: -"Skill display title"
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "content": {
-      "items": {
-        "properties": {
-          "text": {
-            "type": "string"
-          },
-          "type": {
-            "type": "string"
-          }
-        },
-        "type": "object"
-      },
-      "type": "array"
-    }
-  },
-  "type": "object"
-}New value: +null
  4. Changed5 schema fields changed
    • addedInput schema / properties / category / description
      Added value: +"Skill category (e.g. tech, writing, workflow)"
    • addedInput schema / properties / slug / description
      Added value: +"Unique skill identifier"
    • addedInput schema / properties / tags
      Added value: +{
+  "description": "Optional tags for filtering",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / title / description
      Added value: +"Skill display title"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "content": {
+      "items": {
+        "properties": {
+          "text": {
+            "type": "string"
+          },
+          "type": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
  5. Changed5 schema fields changed
    • removedInput schema / properties / category / description
      Removed value: -"Skill category (e.g. tech, writing, workflow)"
    • removedInput schema / properties / slug / description
      Removed value: -"Unique skill identifier"
    • removedInput schema / properties / tags
      Removed value: -{
-  "description": "Optional tags for filtering",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}
    • removedInput schema / properties / title / description
      Removed value: -"Skill display title"
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "content": {
-      "items": {
-        "properties": {
-          "text": {
-            "type": "string"
-          },
-          "type": {
-            "type": "string"
-          }
-        },
-        "type": "object"
-      },
-      "type": "array"
-    }
-  },
-  "type": "object"
-}New value: +null
  6. Changed5 schema fields changed
    • addedInput schema / properties / category / description
      Added value: +"Skill category (e.g. tech, writing, workflow)"
    • addedInput schema / properties / slug / description
      Added value: +"Unique skill identifier"
    • addedInput schema / properties / tags / description
      Added value: +"Optional tags for filtering"
    • addedInput schema / properties / title / description
      Added value: +"Skill display title"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "content": {
+      "items": {
+        "properties": {
+          "text": {
+            "type": "string"
+          },
+          "type": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
  7. Changed1 schema field changed
    • addedInput schema / properties / tags
      Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
  8. Changed1 schema field changed
    • removedInput schema / properties / tags
      Removed value: -{
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}
  9. Changed1 schema field changed
    • addedInput schema / properties / tags
      Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
  10. Added
  11. Removed
  12. Added

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description discloses the key side effect: 'Writes JSON to content/skills/<slug>.json', and the access requirement. This goes beyond the tool name, though it doesn't detail error behavior or reversibility.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no waste, and front-loaded with the main purpose. Every word adds value.

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?

For a simple file-writing mutation, it covers the main behavior and auth prerequisite but lacks details on return values, validation, or handling of optional parameters. Given no output schema or annotations, more could be said, but it's adequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds meaning only for 'slug' via the file path notation, but leaves 'body', 'title', 'category', and 'tags' unexplained. With 0% schema description coverage, this is a significant gap.

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?

The description clearly states the verb ('Create or replace'), the resource ('a skill by slug'), and the scope, distinguishing it from sibling tools like delete_skill and get_skill via the upsert semantics.

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?

It provides clear context that this is owner-only and requires an Authorization Bearer token, implying privileged use. It doesn't explicitly name alternatives, but the purpose statement is clear enough to infer when to use it.

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

All humanMCP — kapoost toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation4/5

Most tools have clearly distinct purposes with detailed descriptions, but a few boundaries are fuzzy: leave_message vs ask_human vs leave_comment, and list_content vs list_collection could confuse an agent at first glance. Overall, the descriptions are thorough enough to disambiguate.

Naming Consistency4/5

The naming convention is predominantly snake_case with verb_noun structure (list_content, read_blob, upsert_skill). Minor deviations exist such as the mysloodsiewnia_* prefix and British spelling in synthesise_persona_patterns, but the pattern is highly recognizable and readable.

Tool Count2/5

At 41 tools, the surface area is very large for a single MCP server and exceeds the 'heavy' threshold. While each tool serves a distinct purpose, the sheer number makes the server feel bloated and harder to navigate; many tools could be grouped or pruned without losing core functionality.

Completeness4/5

The server covers a broad domain: content read/list, personas, skills management, vault CRUD (except update/delete intentionally), provenance, licensing, memory, and async question/narada workflows. Minor gaps exist like no tool to cancel a narada job or update a memory, but these are workable and the core workflows are well supported.

Resources