get_skillRead one skill in full, including the copy-ready quick prompt, inputs, process, decision rules, quality checks, limitations, worked example, and the downloadable SKILL.md URL.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Skill slug, e.g. build-ideal-customer-profile. |
| Name | Required | Description | Default |
|---|---|---|---|
| skill | Yes | ||
| relatedTools | Yes | ||
| relatedPlaybooks | Yes |
Changes observed during successful MCP inspections.
Output schema / (root)Previous value: -nullNew value: +{
+ "$schema": "http://json-schema.org/draft-07/schema#",
+ "additionalProperties": false,
+ "properties": {
+ "relatedPlaybooks": {
+ "items": {
+ "additionalProperties": {},
+ "properties": {
+ "slug": {
+ "type": "string"
+ },
+ "title": {
+ "type": "string"
+ },
+ "url": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "slug",
+ "title",
+ "url"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "relatedTools": {
+ "items": {
+ "additionalProperties": {},
+ "properties": {
+ "name": {
+ "type": "string"
+ },
+ "slug": {
+ "type": "string"
+ },
+ "url": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "slug",
+ "name",
+ "url"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "skill": {
+ "additionalProperties": {},
+ "properties": {
+ "name": {
+ "type": "string"
+ },
+ "skillFileUrl": {
+ "type": "string"
+ },
+ "slug": {
+ "type": "string"
+ },
+ "url": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "slug",
+ "name",
+ "url",
+ "skillFileUrl"
+ ],
+ "type": "object"
+ }
+ },
+ "required": [
+ "skill",
+ "relatedPlaybooks",
+ "relatedTools"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds value by specifying the exact components returned (e.g., copy-ready quick prompt, SKILL.md URL), which is beyond the annotations and helps the agent understand the scope of the read.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single, information-dense sentence that front-loads the core action and then lists the deliverable components without redundancy. Every phrase earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple read tool with one parameter, a rich output schema (not shown but indicated), and annotations covering safety, the description fully specifies what is returned. No missing information an agent would need to call it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the single parameter 'slug' is fully described in the schema with an example. The description adds no additional meaning beyond what the schema provides, so baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a clear verb+resource: 'Read one skill in full' and enumerates the specific content returned (quick prompt, inputs, process, etc.). This distinguishes it from list_skills and other get_* tools by implying it retrieves the complete single skill record.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Implies usage for retrieving full skill details, but does not explicitly contrast with alternatives like list_skills or other get_* tools. No explicit 'when not to use' or naming of sibling tools, leaving some inference required.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.