Sutra

Read a Sutra skill resource

get_skill_resource

Read-onlyIdempotent

Return one supporting file from an enabled Sutra skill by slug and path.

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.

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

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description adds the 'enabled skill' precondition, which is useful, but says nothing about error behavior for missing slugs/paths or the resource size limits beyond the 300-char path constraint.

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 zero filler. Everything an agent needs for a first-pass read is present and nothing is wasted.

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 purpose and the enabled-skill precondition, but a brief note on the get_skill dependency for obtaining the path would have made it fully self-sufficient.

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 parameters are already documented, including the important detail that path must match what get_skill returned. The description only names slug and path without adding format, constraint, or dependency detail beyond the schema, so the 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?

States a specific verb ('Return') and resource ('one supporting file from an enabled Sutra skill'), which cleanly separates it from the sibling get_skill that returns the skill itself. It does not name a sibling explicitly, so it falls short of the 5 tier, but the purpose is unambiguous.

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?

The description implies a prerequisite ('enabled' skill) but gives no explicit when-to-use guidance, no when-not-to-use, and no reference to the alternative get_skill for retrieving the skill definition itself. The agent must infer that it should call get_skill first to discover the path.

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?