cuttingfloor

Read a skill

skills.get

Read-onlyIdempotent

The whole skill as Markdown: when to use it, what it needs, numbered Steps naming the tools to call, a decision table and the rules to keep. Follow the Steps in order.

Input Schema

Name	Required	Description	Default
`slug`	Yes	From skills.search, e.g. "cut-pauses-ums-and-restarts"

Output Schema

Name	Required	Description
`name`	Yes
`slug`	Yes
`author`	Yes	Who wrote the skill; credit them when you name it
`related`	Yes
`version`	Yes
`markdown`	Yes	The whole skill, frontmatter included: follow its Steps
`author_url`	Yes	A link to the author or the work the skill came from; null when there is none
`description`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 5, 2026

addedOutput schema / properties / author

Added value: +{
+  "description": "Who wrote the skill; credit them when you name it",
+  "type": "string"
+}

addedOutput schema / properties / author_url

Added value: +{
+  "anyOf": [
+    {
+      "format": "uri",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "A link to the author or the work the skill came from; null when there is none"
+}

changedOutput schema / required

Previous value: -[
-  "slug",
-  "name",
-  "description",
-  "version",
-  "related",
-  "markdown"
-]New value: +[
+  "slug",
+  "name",
+  "description",
+  "version",
+  "author",
+  "author_url",
+  "related",
+  "markdown"
+]

First observedOct 25, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds valuable behavior beyond that: the payload is a full Markdown procedure document with an ordered Steps list intended to be executed sequentially, which is not derivable from the annotations.

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 short sentences, front-loaded with the return payload and the document structure, ending with the imperative instruction. No filler or repetition.

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?

With an output schema present, the description does not need to restate return values, and it still usefully outlines the document's anatomy and the sequential-execution expectation. The only gap is any mention of what happens when the slug does not match an existing skill.

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 coverage is 100% and the slug property already documents its format and its origin ('From skills.search, e.g. ...'). The description adds no further meaning about slug resolution or behavior on an unknown slug, so the baseline of 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 resource and what it returns: the whole skill as Markdown, enumerated as when-to-use, requirements, numbered Steps, decision table and rules. That is clearly distinct from siblings like skills.search, although the contrast is only implied by the schema's 'From skills.search' note rather than stated in the description itself.

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

Usage Guidelines3/5

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

'Follow the Steps in order' tells the agent how to act on the result, which is useful usage guidance for a procedure document. It does not say when to call this versus skills.search, nor any precondition such as resolving a slug first — that routing only appears inside the parameter schema.

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

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