Skip to main content
Glama

SkillU

get_skill

Get the full detail of one SkillU Agent Skill by its slug: description, workflow steps, supported agents, tier, version and detail-page URL.

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
slugYesThe skill slug, e.g. blender-scene-assistant.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden; it does convey that this is a single-record retrieval returning static descriptive fields (steps, agents, tier, version, URL), which implies a read-only lookup. It omits error behavior for missing slugs, permissions, and any caching or freshness characteristics.

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?

A single front-loaded sentence with the operation first and the returned fields enumerated after the colon; there is no redundant or filler text.

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 one-parameter read tool this is nearly complete: the description enumerates the returned fields, standing in for the absent output schema. The remaining gap is the absence of any failure-mode or fallback guidance for an unrecognized slug.

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 100% and the schema already documents slug with an example, so the baseline is 3. The description adds only the phrase 'by its slug' and no further format, casing, or lookup-failure semantics beyond the schema.

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 ('Get the full detail of one SkillU Agent Skill') and scopes it to a single record identified by slug, which contrasts implicitly with the list/search siblings. It stops short of naming search_skills or list_categories, so differentiation must be inferred from the singular-vs-multi semantics.

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?

Usage is only implied: an agent can infer it should call this when it already has a slug and needs full detail rather than a list. There is no explicit when-to-use or when-not-to-use statement, and no guidance on what to do when the slug is unknown (e.g., fall back to search_skills).

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