agentskills-mcp

Get Skill Metadata

get_skill_metadata

Retrieve lightweight frontmatter metadata (name, version, description, tags) for a known skill ID when you need its catalog entry without fetching the full skill body.

Instructions

Return lightweight metadata for a single skill (frontmatter only — name, version, description, tags). Cheaper than get_skill_body when you only need the catalog entry for a known skill_id.

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_id": "<skill_id>"
    },
    "name": "get_skill_metadata"
  }
}

Input Schema

Name	Required	Description	Default
`skill_id`	Yes	Directory name of the skill, as returned by list_skills().

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.1Nov 4, 2026

TDQS

A4.5/5.0

Behavior4/5

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

No annotations are supplied, so the description carries the full burden. It discloses the exact scope of the returned payload (frontmatter only, listing the four fields) and a cost characteristic ('cheaper than get_skill_body'), which is genuinely useful behavioral context. It stops short of stating that the call is read-only and side-effect free, which is only implied by 'Return'.

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?

Two clauses, zero filler, with the payload scope front-loaded before the cost/alternative comparison. Every phrase adds information an agent would otherwise have to infer.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (one required string param), an output schema exists so return-value detail is unnecessary, and the description still covers scope, cost, and the alternative. Nothing needed to invoke it correctly is missing.

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?

There is a single parameter with 100% schema description coverage, so the schema already explains that skill_id is the directory name returned by list_skills(). The description only restates the 'known skill_id' precondition and adds no format or validation detail beyond that. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

States a specific verb and resource ('Return lightweight metadata for a single skill') and bounds the payload precisely with the parenthetical 'frontmatter only — name, version, description, tags'. It explicitly separates itself from the sibling get_skill_body, so an agent can pick between them without opening either schema.

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?

Gives an explicit selection rule: use this when you only need the catalog entry for a known skill_id, and names get_skill_body as the heavier alternative. Combined with the schema's note that skill_id comes from list_skills(), the prerequisite for calling it is also covered.

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

Deploy Server