Skip to main content
Glama

Moltline Studio

by com.moltlinestudio

Get Full Skill

get_full_skill
Read-onlyIdempotent

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

Typical input {"slug": "inbox-zero-assistant", "skill_name": "Deep 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.

Input Schema

TableJSON 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

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint. The description adds that the tool never raises protocol errors and returns error objects with fix instructions, which is valuable beyond annotations. 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?

Every sentence serves a purpose: purpose, plan indicator, example, usage guidance, error behavior, safety note. Well-structured with no fluff.

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 params, output schema present, rich annotations), the description covers purpose, when to use, error handling, idempotency, and parameter constraints. Complements output schema and sibling list fully.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with good descriptions. The description adds context: slug must be exactly as from search_catalog, skill_name must match preview_product's list, and provides a concrete example. This adds value beyond the schema.

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 clearly states the tool loads a paid skill's complete instructions from a product, specifies it is for premium paid plans, and distinguishes itself from siblings like get_free_skill and get_full_product by naming them directly.

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 says 'Use after preview_product has shown the skill list' and provides alternatives for free skills (get_free_skill) and bulk retrieval (get_full_product). Also notes idempotency for safe retry after errors.

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
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
Disambiguation4/5

The tools are mostly distinct, but the four get_full_* tools (kit, persona, product, skill) share a similar naming pattern and could be confused. Descriptions clarify the different payloads, so an agent can select correctly with careful reading.

Naming Consistency5/5

All tool names follow a consistent lowercase snake_case verb_noun pattern (get_free_skill, list_kits, search_catalog, etc.). The verbs vary by action but the structure is uniform and predictable.

Tool Count5/5

10 tools cover catalog search, recommendation, preview, and tiered content retrieval. This is well-scoped for a product catalog server, neither too few nor too many.

Completeness4/5

The surface covers browsing, searching, recommending, previewing, and retrieving free/full content, plus upgrade info. Minor gap: per-product pricing is not available except for kits, so agents cannot quote individual product prices directly.

Resources