Sutra

Read a Sutra skill resource

get_skill_resource

Read-onlyIdempotent

Read one supporting file from an enabled Sutra skill.

Use only for a path listed by get_skill and only when needed for the current task. Do not guess paths or load every resource preemptively.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`path`	Yes	Relative resource path exactly as returned by get_skill.
`slug`	Yes	Slug of the enabled skill that owns the resource.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`path`	Yes
`content`	Yes
`encoding`	Yes
`size_bytes`	Yes
`content_type`	Yes

Schema Changelog

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

Changed10 schema fields changedSep 2, 2026

addedInput schema / properties / path / description

Added value: +"Relative resource path exactly as returned by get_skill."

addedInput schema / properties / path / maxLength
```
Added value: +300
```
addedInput schema / properties / path / minLength
```
Added value: +1
```

addedInput schema / properties / slug / description

Added value: +"Slug of the enabled skill that owns the resource."

addedInput schema / properties / slug / maxLength
```
Added value: +100
```
addedInput schema / properties / slug / minLength
```
Added value: +1
```
addedInput schema / properties / slug / pattern
```
Added value: +"^[a-z0-9]+(?:-[a-z0-9]+)*$"
```
removedOutput schema / additionalProperties
```
Removed value: -true
```

addedOutput schema / properties

Added value: +{
+  "content": {
+    "type": "string"
+  },
+  "content_type": {
+    "type": "string"
+  },
+  "encoding": {
+    "enum": [
+      "utf-8",
+      "base64"
+    ],
+    "type": "string"
+  },
+  "path": {
+    "type": "string"
+  },
+  "size_bytes": {
+    "type": "integer"
+  }
+}

addedOutput schema / required

Added value: +[
+  "path",
+  "content_type",
+  "size_bytes",
+  "encoding",
+  "content"
+]

First observedSep 2, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds useful behavioral constraints: the tool reads exactly one file, requires the skill to be enabled, and expects the path to come from get_skill. These are not visible in the annotations and help the agent anticipate failure modes.

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 short sentences carry a complete and scannable message: what the tool does, when to use it, and what to avoid. No filler or repetition; the purpose is front-loaded.

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?

For a simple read tool with two fully described parameters, an output schema, and annotations covering safety, the description covers the essential operational constraints (enabled skill, path from get_skill, single-file read, no preemptive use). Nothing critical is missing for correct invocation.

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 both params (path and slug) are already documented accurately. The description reinforces the path parameter's origin ('exactly as returned by get_skill') but adds no new semantic detail beyond what the schema provides. Baseline 3 is appropriate.

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 states a specific verb and resource: 'Read one supporting file from an enabled Sutra skill.' It clearly distinguishes itself from sibling tools like get_skill (which lists paths) and upload_skill/write_observation (which write). The singular 'one' also differentiates it from bulk-loading tools.

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?

The description explicitly says when to use the tool: 'only for a path listed by get_skill and only when needed for the current task.' It also provides exclusions: 'Do not guess paths or load every resource preemptively.' This gives clear decision guidance with reference to the alternative tool.

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

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

Need Help?