Skip to main content
Glama

Get skill

get_skill
Read-onlyIdempotent

Return a granted Ready skill by default, or select target=my_draft to inspect only this user's unreviewed Draft package.

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"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes
targetNo

Output Schema

NameRequiredDescriptionDefault
dataYes
viewYes
workspaceNo
generated_atYes
schema_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description's added value is access scoping: only granted Ready skills are returned, and my_draft is restricted to this user's own unreviewed package. It does not describe not-found or not-granted error behavior, which keeps it below 5.

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?

One sentence with the default behavior front-loaded and the alternate mode following. No redundant restatement of the title or annotations.

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 a rich annotation set and an output schema present, the description need not explain return values, and it covers the scoping and mode selection an agent needs. Only the slug semantics and failure cases are absent, which is a modest gap for a 2-parameter read tool.

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 0%, so the description must carry the load: it explains both enum values of target, including that 'ready' is the default. The required slug parameter is left entirely unexplained beyond its name, so compensation is only partial.

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?

States a concrete verb ('Return') and resource ('Ready skill') plus an explicit alternate mode for Draft packages. An agent can tell it retrieves a single skill rather than listing or updating one, though it does not distinguish itself from siblings like get_collection by name.

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?

Gives the selection condition for the only optional parameter: default returns the granted Ready skill, target=my_draft inspects the user's unreviewed Draft. It does not say when to prefer this over check_skill_updates or list_my_skills, so alternative routing is only implied.

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.

Resources