Skip to main content
Glama
Sign In
skills.sh MCP Server

skills.sh MCP Server

by ANeuronI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

get_skill_details

Retrieve detailed information about a specific skill to evaluate its suitability. Use after searching skills to access install counts, weekly installs, and supported platforms.

Instructions

Get detailed information about a specific skill. Use this tool ALWAYS after 'search_skills' to vet a skill before recommending it. It provides critical data like total installs, weekly installs, and supported platforms. Extract 'owner', 'repo', and 'skillId' from the search results table.

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": {
      "owner": "<owner>",
      "repo": "<repo>",
      "skillId": "<skillId>"
    },
    "name": "get_skill_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoYesRepository name
ownerYesGitHub owner/username
skillIdYesSkill ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.4

TDQS

A4.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It mentions the tool provides 'critical data like total installs, weekly installs, and supported platforms,' but does not explicitly state it is read-only or disclose other behavioral traits like rate limits. Adequate but not exhaustive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with purpose. Concise with no wasted words, though it could be slightly more compressed without losing clarity.

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?

Given no output schema, the description sufficiently explains the kind of data returned (installs, platforms). Combined with high schema coverage, it provides a complete picture for a simple retrieval tool.

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 parameters are already described. The description adds value by instructing to 'Extract owner, repo, and skillId from the search results table,' which clarifies source and usage beyond schema definitions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Get detailed information about a specific skill,' which is a specific verb+resource. It distinguishes from siblings by instructing to use after 'search_skills' and naming sibling tools.

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?

Explicitly states 'Use this tool ALWAYS after search_skills to vet a skill before recommending it,' providing clear context of when to use and a prerequisite.

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

Deploy Server

Other Tools