Skip to main content
Glama

Moltline Personal Suite

by com.moltlinestudio

Get Full Skill

get_full_skill
Read-onlyIdempotent

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

Typical input {"slug": "inbox-assistant", "skill_name": "Zero Sweep"} 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
NameRequiredDescriptionDefault
slugYesProduct slug exactly as returned by list_products.
skill_nameYesExact skill name as listed in that product's "skills" array from list_products.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A5/5.0
Behavior5/5

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

Annotations already cover readOnlyHint, idempotentHint, and destructiveHint. The description adds that the tool returns an error object instead of raising protocol errors, and confirms idempotency and retry safety. 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?

The description is well-structured: first sentence states purpose, then example, then usage guidance, then error behavior, then safety note. It is concise, front-loaded, and every sentence earns its place.

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 output schema exists, the description covers purpose, usage, error handling, and safety. It is fully complete for a read-only, idempotent tool with clear error responses.

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

Parameters5/5

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

Both parameters are fully described in the schema (100% coverage). The description adds an example with specific values, explains constraints (slug from list_products, skill_name from skills array), and provides error handling context.

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 verb 'Load' and the resource 'one paid skill's complete instructions from a product'. It differentiates from siblings by explicitly naming get_free_skill and get_full_product, and provides an example input/output.

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?

The description explicitly says 'Use when the caller wants one specific paid skill' and 'Not for the free gateway skill... not for every skill at once'. It also covers error handling and retry safety.

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

All Moltline Personal Suite 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.4/5.0
Disambiguation4/5

Most tools target distinct purposes (budgeting, counting days, skills, finances, scheduling, bill splitting). However, budget_split and savings_goal both deal with personal finance and could be confused by an agent, though their descriptions clarify the difference. Also, get_free_skill, get_full_skill, and get_full_product are related but clearly distinguished by access level and scope.

Naming Consistency4/5

Tool names use a consistent snake_case verb_noun pattern (e.g., budget_split, countdown_days, savings_goal). The only minor deviation is that some verbs are adjectives (free, full) rather than actions, but the pattern is still predictable and readable.

Tool Count5/5

With 9 tools, the set is well-scoped for a personal finance and productivity assistant. Each tool addresses a distinct, useful function without overwhelming the agent or leaving trivial gaps.

Completeness4/5

The tool surface covers key personal tasks: budgeting, savings goals, event countdowns, spaced repetition, bill splitting, and product exploration. A minor gap is the lack of a tool for expense tracking or recurring bills, but the domain is well-covered for the stated purpose.

Resources