Moltline Business Suite

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

Name	Required	Description	Default
`slug`	Yes	Product slug exactly as returned by list_products, e.g. "smb-ops-desk"; must be non-empty.
`skill_name`	Yes	Exact 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

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?

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds valuable context beyond annotations: the PREMIUM license requirement, the error behavior (never raises protocol error, returns an error object with fix), and that retrying after correcting input is always safe. This exceeds the baseline set by annotations.

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 front-loaded with the primary purpose, then includes a concise example, usage guidance, error handling, and safety note. Every sentence adds distinct value and the structure is easy to scan.

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 complexity (premium license, sibling differentiation, error behavior), the description covers all necessary context: what it returns, when to use it, how errors manifest, and idempotency. An output schema exists so detailed return fields are not required. The description is complete for an agent to select and invoke the tool correctly.

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%, with both parameters documented including examples from list_products. The description provides a typical input example and reinforces skill_name selection, but it mostly repeats what the schema already conveys. Baseline 3 is appropriate since the schema does the heavy lifting.

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 and resource: 'Load one paid skill's complete instructions from a product.' It clearly differentiates from siblings by stating it is for one specific paid skill, not the free gateway skill (get_free_skill) or all skills at once (get_full_product).

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 guidance is provided: 'Use when the caller wants one specific paid skill.' It also names what it is not for, citing get_free_skill and get_full_product as alternatives, making the selection criteria unambiguous.

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 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: four financial calculators (cash_runway, loan_payment, target_price, unit_economics) each solve a different numeric problem, and four product/skill accessors (list_products, get_free_skill, get_full_skill, get_full_product) serve different retrieval needs. There is no overlap or ambiguity between tools.

Naming Consistency4/5

Tool names follow two internally consistent patterns: financial calculators use noun phrases (cash_runway, loan_payment) while product/skill tools use verb_noun style (list_products, get_free_skill). This grouping into predictable conventions is mostly consistent, but the mixed patterns across the two categories are a minor deviation from a single uniform style.

Tool Count5/5

With 8 tools, the server is well-scoped. Each financial calculator and product accessor earns its place, and the count is neither too thin nor too heavy for the stated 'Business Suite' purpose.

Completeness5/5

The financial tools cover the core calculations (runway, loan payment, target price, unit economics including break-even), and the product tools provide a complete access path from listing products to retrieving free skills, full skills, and full product details. There are no obvious dead ends or missing operations within the server's declared domain.

Resources

Need Help?