Skip to main content
Glama

NS Pros MCP Gateway

aws-mcp__aws___retrieve_skill

Retrieve an AWS skill (workflows, references). Returns SKILL.md, or file if given.

Call search_documentation FIRST and copy skill_name verbatim -- it is an opaque registry ID. Never guess or fabricate skill_name or file.

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": {
      "skill_name": "<skill_name>"
    },
    "name": "aws-mcp__aws___retrieve_skill"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNoOptional file path within the skill, copied as cited (e.g. `references/architecture.md`). Don't add or strip a `references/` prefix. Omit for SKILL.md.
skill_nameYesRequired. Exact `skill_name` from a search_documentation result, copied verbatim. Do not invent or modify.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it states the return shape (SKILL.md by default, a specific file otherwise) and warns that skill_name is an opaque registry ID that must not be fabricated. It omits auth requirements, result size, and failure behavior when an invalid ID is supplied.

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 with the purpose and return value front-loaded, then the mandatory prerequisite, then the anti-fabrication warning. No sentence is redundant.

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?

For a two-parameter read tool with no annotations and no output schema, the description covers purpose, prerequisite, return value, and the key failure mode. It could go further by explaining how an agent discovers available `file` paths within a skill, but the essentials for a correct call are present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns the extra point by adding provenance semantics the schema only partly conveys -- the ID is opaque and must originate from a search_documentation call. The file-parameter meaning is left almost entirely to the schema text, which already handles it well.

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?

The description states a specific verb and resource ('Retrieve an AWS skill') and even discloses the return value ('Returns SKILL.md, or `file` if given'), which an agent can act on without opening the schema. It is distinguishable from sibling search_documentation by the explicit two-step routing, though it never names a non-use case.

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?

It prescribes the exact sequencing: call `search_documentation` FIRST, then copy `skill_name` verbatim. The alternative (search) and the condition that selects it (you need a valid opaque ID) are both spelled out, and the 'never guess or fabricate' line blocks the most likely misuse.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.