Moltline Creator Studio

Get Full Skill

get_full_skill

Read-onlyIdempotent

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

Typical input {"slug": "brand-voice", "skill_name": "Voice Audit"} returns {"slug": ..., "skill": ..., "instructions": ""}.

Returns one named skill, selected by skill_name. Use when 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.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	Yes	Product slug exactly as returned by list_products.
`skill_name`	Yes	Exact skill name as listed in that product's "skills" array from list_products.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

TDQS

A4.7/5.0

Behavior5/5

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

Description adds significant behavioral context beyond annotations: error handling details ('never raises a protocol error — it returns an error object'), retry safety, and idempotency. Annotations already declare readOnlyHint and idempotentHint, and the description reinforces these with practical implications. No contradiction.

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?

Description is well-structured: front-loaded with main purpose, then example, usage guidelines, error handling, and idempotency note. Every sentence adds value with no redundant or vague phrasing.

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?

Given the tool's simplicity (2 parameters, 100% schema coverage, clear annotations, output schema), the description is complete. It covers purpose, usage, error behavior, and safety, leaving no gaps for an agent to infer.

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%, so the schema already documents both parameters well. The description provides an example but does not add new semantic meaning beyond what the schema provides. Baseline 3 is appropriate.

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?

Description clearly states the tool loads one paid skill's complete instructions from a product. It provides a typical input/output example and distinguishes from siblings: get_free_skill for free gateway skill and get_full_product for all skills at once. The verb 'load' is specific and the resource is well-defined.

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?

Explicitly states when to use: 'Use when the caller wants one specific paid skill.' Also lists exclusions: 'Not for the free gateway skill... and not for every skill at once (get_full_product).' This provides clear guidance on tool selection among siblings.

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

All Moltline Creator Studio tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.7/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose: prose analysis, headline scoring, reading stats, platform length check, product listing, free/paid skill retrieval, and full product details. There is no ambiguity between any pair of tools, and descriptions explicitly note what not to use them for.

Naming Consistency5/5

All tool names use consistent snake_case verbs followed by nouns (e.g., analyze_writing, list_products, get_free_skill). Even reading_time and social_length_check follow the pattern, albeit with nouns first, but the style is uniform and predictable.

Tool Count5/5

With 8 tools, the server is well-scoped. It covers both content analysis (4 tools) and product catalog access (4 tools) without overloading or underrepresenting either domain. The number feels appropriate for a focused studio toolkit.

Completeness4/5

The tool set covers the core functions of a Creator Studio: writing analysis, headline optimization, reading time, social length checks, plus full product catalog introspection. Minor gaps like grammar checking or content generation exist but are outside the stated scope. The set has no dead ends for the intended workflows.

Resources

Need Help?