humanMCP — 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

Name	Required	Description	Default
`body`	Yes
`slug`	Yes
`tags`	No
`title`	Yes
`category`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedAug 13, 2026

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."

Changed1 schema field changedJul 21, 2026

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"
+}

Changed5 schema fields changedMay 20, 2026

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

Changed5 schema fields changedMay 20, 2026

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"
+}

Changed5 schema fields changedMay 20, 2026

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

Changed5 schema fields changedMay 5, 2026

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"
+}

Changed1 schema field changedApr 27, 2026

addedInput schema / properties / tags

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

Changed1 schema field changedApr 23, 2026

removedInput schema / properties / tags

Removed value: -{
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

Changed1 schema field changedApr 22, 2026

addedInput schema / properties / tags

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

AddedApr 14, 2026
RemovedApr 14, 2026
AddedApr 11, 2026

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 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.

upsert_skill

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources