Skip to main content
Glama
Sign In

Moltline Studio

by com.moltlinestudio
OverviewDiscussionsAdmin

Get Full Skill

get_full_skill
Read-onlyIdempotent

Load one paid skill's complete instructions from a product. PREMIUM (license).

Typical input {"slug": "inbox-commander", "skill_name": "email-triage"} returns {"slug": ..., "skill": ..., "instructions": ""}.

Returns one named skill, selected by skill_name. Use after preview_product has shown the skill list and the caller wants one specific paid skill. Not for the free gateway skill, which get_free_skill returns with no plan, and not for every skill at once (get_full_product). Errors: on invalid, missing, or malformed input this tool never raises a protocol error; it returns {"error": ""} (for example {"error": "unknown slug ''"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

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>",
      "skill_name": "<skill_name>"
    },
    "name": "get_full_skill"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesProduct slug exactly as returned by search_catalog.
skill_nameYesExact skill name as shown in preview_product's "skills" list for that product.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (readOnly/idempotent/non-destructive), the description discloses the error contract: no protocol errors are raised, failures return {"error": "..."} with an example, and retry after correction is safe. It also flags the premium license dimension, which the annotations do not cover.

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?

Front-loaded with purpose, then alternatives, then error behavior — a sensible order with no filler sentences. The 'Typical input ... returns ...' block is somewhat redundant given a full output schema exists and could be trimmed.

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?

Covers preconditions (must preview first), alternatives, error and retry semantics, and license gating — everything needed to invoke it correctly. Since an output schema exists, the description is not obligated to detail return values further.

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 coverage is 100%, and the schema already states that slug comes from search_catalog and skill_name from preview_product's skills list. The description's example input restates that relationship but adds little new semantics, so the baseline of 3 applies.

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 opens with a specific verb and resource: 'Load one paid skill's complete instructions from a product.' It immediately constrains scope to a single paid skill, which distinguishes it from get_full_product (all skills) and get_free_skill (free gateway skill) 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 Guidelines5/5

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

Explicit when-to-use: 'Use after preview_product has shown the skill list and the caller wants one specific paid skill.' Explicit when-not-to-use with named alternatives for both the free path (get_free_skill) and the bulk path (get_full_product), plus a note that it is premium/licensed.

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

All Moltline Studio toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources