Skip to main content
Glama
@skills-hub-ai/mcp

@skills-hub-ai/mcp

get_skill_detail

Retrieve an installed skill's full details by slug, including instructions, composition children, and metadata, plus a skills-hub.ai link to share with users.

Instructions

Get full details about a skill including instructions, composition children, and metadata. The result includes a url to the skill's page on skills-hub.ai; show that link to the user.

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": {
      "slug": "<slug>"
    },
    "name": "get_skill_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesSkill slug (e.g. 'review-code')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.13

TDQS

B3.4/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 behavioral burden. It usefully states that the result includes instructions, composition children, metadata, and a URL, and instructs showing the URL to the user. It does not disclose error behavior, permissions, or whether the operation is read-only, though the 'get' verb strongly implies a safe read.

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?

The description is two sentences, front-loaded with the purpose and followed by a useful output instruction. Every sentence earns its place and there is no unnecessary wording.

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 simple one-parameter read tool with no output schema, the description covers the return contents at a high level and provides a user-facing instruction about the URL. It is mostly complete, though it could mention what happens if the skill slug is not found.

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?

The schema fully documents the single required slug parameter with an example. The description adds no further meaning about the slug beyond the schema, so the baseline score of 3 is appropriate.

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 clear verb and resource: get full details about a skill. It also enumerates the kinds of details returned, which makes the purpose concrete. However, it does not explicitly differentiate itself from sibling tools like search_skills or list_installed_skills.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use this tool versus alternatives. The agent can infer that it is for retrieving detail, but the description does not say to use it after search or instead of list_installed_skills.

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