Skip to main content
Glama

Moltline Business 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": "smb-ops-desk", "skill_name": "invoice-chaser"} 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, e.g. "smb-ops-desk"; must be non-empty.
skill_nameYesExact skill name as listed in that product's "skills" array from list_products, e.g. "invoice-chaser"; must be non-empty.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds valuable behavioral context beyond annotations: it never raises a protocol error but returns an {"error": ...} object with fix guidance, and explicitly notes retry safety after correcting input. This supplements the annotation coverage.

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?

The description is well-structured and front-loaded with purpose, then example, usage, error behavior, and safety. It is slightly repetitive ('Returns one named skill' re-states the purpose) but overall every section earns its place and it is not bloated.

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 that an output schema exists, the description need not detail return fields, but it still covers the example return shape. It covers usage context, exclusions, error handling, and idempotent retry behavior. This is complete for a moderate-complexity tool with strong annotations.

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 baseline is 3. The description adds an example input and clarifies skill_name's role ('selected by skill_name'), but the schema already documents both parameters with examples and constraints. No additional meaning is critical.

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 starts with a specific verb+resource: 'Load one paid skill's complete instructions from a product.' It clearly distinguishes from siblings by explicitly contrasting with get_free_skill and get_full_product, naming what this tool returns (one named skill).

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?

Provides explicit guidance: 'Use when the caller wants one specific paid skill.' It also states exclusions: 'Not for the free gateway skill... and not for every skill at once (get_full_product)', naming the alternative tools. This is clear when-to-use and when-not-to-use guidance.

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

All Moltline Business 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
Disambiguation3/5

The financial calculation tools (cash_runway, loan_payment, target_price, unit_economics) are clearly distinct in their inputs and outputs. However, within the product listing tools (list_products, get_free_skill, get_full_skill, get_full_product), the differentiation relies heavily on the 'FREE' vs 'PREMIUM' tags and the notion of 'free gateway skill' vs 'paid skills', which creates some ambiguity. An agent could easily pick get_free_skill when it actually needs get_full_skill.

Naming Consistency4/5

The tool set uses a mix of verb_noun (list_products, get_free_skill, get_full_product) and simple noun phrases (cash_runway, loan_payment, target_price, unit_economics). While the 'get_*' prefix creates a consistent pattern for product/skill access, the standalone financial calculation tools break this pattern. Nevertheless, the naming is still clear and predictable within each subgroup.

Tool Count5/5

With 8 tools, the set is well-scoped for a 'business' server that covers two clear domains: financial calculations (4 tools) and product/skill browsing (4 tools). Each tool covers a distinct operation without redundancy, and the count feels appropriate for the stated purpose.

Completeness3/5

The financial calculation tools cover common business math (runway, loan payments, margin/pricing, break-even), but lack coverage for revenue metrics (e.g., ARR, MRR), ROI, or depreciation. The product browsing tools provide a clear CRUD-like flow (list -> get), but there is no way to search or filter products, and the missing 'search_catalog' is referenced as existing on another server. This is a minor gap that may require agents to switch servers.

Resources