Skip to main content
Glama

Sutra

by com.onrender.sutra-c3or

Upload a Sutra skill

upload_skill

Upload a SKILL.md and optional text resources when the user explicitly asks.

Do not create or upload a skill based on inference or without clear authorization. The new version remains disabled until the user enables it in the dashboard.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesHuman-readable skill name containing at least one letter or number.
skill_mdYesComplete UTF-8 SKILL.md text with YAML frontmatter; maximum encoded size is 256 KB.
resourcesNoOptional map of up to 50 relative file paths to UTF-8 text contents; total upload limit is 512 KB.
descriptionNoOptional short description of the skill's purpose.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusYes
messageYes
versionYes

Schema Changelog

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

  1. Changed12 schema fields changed
    • 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"
+]
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already mark this as a non-read-only, non-idempotent mutation. The description adds a key behavioral consequence not in metadata: 'The new version remains disabled until the user enables it in the dashboard.' This is useful, though it doesn't clarify whether an existing active skill is replaced immediately.

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?

Three sentences with no filler; the main action and condition are front-loaded, followed by a guardrail and a post-upload consequence. Each sentence adds distinct value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given full schema descriptions and an output schema, the description covers the essential selection criteria (explicit user request), the authorization boundary, and the unexpected disabled-by-default state. It is complete enough for an agent to invoke the tool correctly; the destructiveHint=false annotation further implies existing versions remain intact.

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 fully documents name, skill_md, resources, and description. The description's mention of 'SKILL.md and optional text resources' aligns with those fields but adds no parameter details beyond the schema.

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 opens with 'Upload a SKILL.md and optional text resources,' which is a specific action and resource. It also adds the condition 'when the user explicitly asks,' making the tool's scope immediately distinct from sibling read/export tools like list_skills or get_skill.

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

Usage Guidelines5/5

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

It states exactly when to use the tool: when the user explicitly asks, and explicitly forbids inference-based or unauthorized uploads. This gives an agent a clear go/no-go condition, even though it doesn't name sibling alternatives.

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

All Sutra 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

A4.4/5.0
Disambiguation5/5

Each tool has a clearly scoped purpose, and the descriptions include explicit usage rules that prevent overlap. Memory retrieval is split into read_context, search_memory, get_cluster, and export_all with distinct trigger conditions, so agents can reliably choose the right tool.

Naming Consistency5/5

All tools use a consistent lower_snake_case verb_noun pattern such as list_clusters, get_skill, search_memory, write_observation, and upload_skill. The naming is predictable and uniform across the entire set.

Tool Count5/5

Ten tools is well-scoped for a personal memory and skills server: it covers memory access, skill access, discovery, writing observations, and export. Each tool earns its place without the set feeling bloated or thin.

Completeness3/5

The server covers discovery, retrieval, saving observations, and uploading skills, but it lacks update/delete operations for memories and skill management beyond upload. This leaves a notable lifecycle gap: incorrect or obsolete saved observations cannot be removed or corrected in place.

Resources