suede-skills-mcp

Get Suede Skill

get_suede_skill

Read-onlyIdempotent

Retrieve details for a named Suede skill, and optionally include its full SKILL.md instructions for setup or review.

Instructions

Return details for one Suede skill, optionally including its full SKILL.md instructions.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "get_suede_skill"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	Skill name, with or without a leading dollar sign.
`includeBody`	No	Include the skill's SKILL.md instructions instead of catalog metadata only.

Output Schema

Name	Required	Description	Default
`body`	No
`found`	Yes
`skill`	No
`bodyTruncated`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value by disclosing the payload-shape tradeoff: by default you get catalog metadata, and only with includeBody do you get the full SKILL.md instructions — behavior that matters for context budgeting and is not in 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?

A single front-loaded sentence with no filler; the optional-body behavior is the only qualifier and it belongs there. Nothing could be removed without losing information.

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 needn't explain return values, and two fully documented parameters keep the surface small. The only gap is the absence of explicit routing guidance to sibling discovery tools, which would matter for an agent unfamiliar with the Suede catalog.

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 leading-dollar-sign tolerance and the includeBody meaning. The description's phrase "catalog metadata only" restates the schema rather than adding format or edge-case detail, so 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?

"Return details for one Suede skill" gives a specific verb (return details) and resource (one Suede skill), and the word "one" distinguishes it from the sibling list_suede_skills and search_suede_skills. It stops short of naming those siblings explicitly, so the differentiation is implied rather than stated.

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?

The singular framing implies this is the lookup-by-name path and the siblings are the browse/search paths, but no explicit when-to-use or when-not-to-use condition is stated. An agent must infer from the tool name and sibling names that list/search should be preferred for discovery.

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

Deploy Server