Sutra

Upload a Sutra skill

upload_skill

Upload a user-authorized SKILL.md and optional text resources in a disabled state.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Human-readable skill name containing at least one letter or number.
`skill_md`	Yes	Complete UTF-8 SKILL.md text with YAML frontmatter; maximum encoded size is 256 KB.
`resources`	No	Optional map of up to 50 relative file paths to UTF-8 text contents; total upload limit is 512 KB.
`description`	No	Optional short description of the skill's purpose.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`status`	Yes
`message`	Yes
`version`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedSep 2, 2026

changedInput schema / properties / description / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maxLength": 500,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / description / description

Added value: +"Optional short description of the skill's purpose."

addedInput schema / properties / name / description

Added value: +"Human-readable skill name containing at least one letter or number."

addedInput schema / properties / name / maxLength
```
Added value: +80
```
addedInput schema / properties / name / minLength
```
Added value: +1
```

changedInput schema / properties / resources / anyOf

Previous value: -[
-  {
-    "additionalProperties": {
-      "type": "string"
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {
+      "type": "string"
+    },
+    "maxProperties": 50,
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / resources / description

Added value: +"Optional map of up to 50 relative file paths to UTF-8 text contents; total upload limit is 512 KB."

addedInput schema / properties / skill_md / description

Added value: +"Complete UTF-8 SKILL.md text with YAML frontmatter; maximum encoded size is 256 KB."

addedInput schema / properties / skill_md / minLength
```
Added value: +1
```
removedOutput schema / additionalProperties
```
Removed value: -true
```

addedOutput schema / properties

Added value: +{
+  "message": {
+    "type": "string"
+  },
+  "status": {
+    "const": "disabled",
+    "type": "string"
+  },
+  "version": {
+    "type": "integer"
+  }
+}

addedOutput schema / required

Added value: +[
+  "status",
+  "version",
+  "message"
+]

First observedSep 2, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the safety profile is covered. The description adds two genuinely non-structured facts: the input must be user-authorized (an auth precondition) and the upload lands 'in a disabled state' (not immediately active). That extra behavioral context is valuable and above the annotation baseline.

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?

A single front-loaded sentence with the verb first and no filler. Every word carries meaning and nothing needs trimming.

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?

An output schema exists, so return values need no explanation, and annotations carry the safety profile. The description covers the input material and the resulting disabled state, which is enough to call it correctly; only edge behavior (duplicate names, overwrite handling) is unaddressed.

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 the schema already documents name, skill_md, resources, and description with constraints (size limits, path map, maxProperties). The description mentions SKILL.md and text resources but adds no syntax, format, or default detail beyond the schema. 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?

The description states a specific verb (upload) and resource (a user-authorized SKILL.md plus optional text resources) with a clear end state (disabled). It is easy to distinguish from read-side siblings like get_skill and list_skills, though it does not explicitly name an alternative. Clear but no sibling differentiation by name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance, no conditions for choosing this over siblings, and no exclusions. 'User-authorized' hints at a precondition but the agent is left to infer usage entirely from the verb.

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

All Sutra tools Inspect

Try in Browser

Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?