Moltline Research Desk

Get Free Skill

get_free_skill

Read-onlyIdempotent

Load a product's free gateway skill with its complete instructions. FREE.

Typical input {"slug": "thesis-advisor"} returns {"slug": ..., "skill": "", "instructions": ""}.

Returns exactly one skill - the product's free gateway skill - chosen automatically from the slug, with no plan required. Use when the caller wants usable instructions immediately. Not for the product's other skills: those are named and need get_full_skill with a skill_name, which requires a paid plan. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": ""} (for example {"error": "unknown slug ''. Use list_products."}). 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. "thesis-advisor".

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already mark readOnlyHint and idempotentHint as true. The description adds value by detailing error handling (returns error object with fix suggestions), the automatic skill selection from slug, and that no plan is required—all beyond the annotations.

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-organized with a purpose statement, example, and key details. It is slightly lengthy but every sentence contributes meaning; no redundancy.

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 simple one-parameter tool, the existence of an output schema, and thorough coverage of usage, errors, and side effects, the description is complete. It does not omit necessary information.

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?

Schema coverage is 100% for the single slug parameter. The description adds context: slug format ('exactly as returned by list_products'), an example, and behavior for invalid input (returns error). This exceeds the schema description.

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 product's free gateway skill with complete instructions. It specifies the return structure and distinguishes itself from get_full_skill, which requires a skill_name and a paid plan.

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 usable instructions immediately.' Contrasts with get_full_skill for other skills, and notes the tool is read-only and idempotent, implying safe retry.

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

All Moltline Research Desk 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 targets a distinct function: statistics tools for descriptive, inferential, and planning; product tools for listing, free skill, paid skill, and full product; and citation formatting. No overlap or ambiguity.

Naming Consistency4/5

Most tools follow a verb_noun or noun_verb pattern, but there is a mix: some are noun phrases (confidence_interval, sample_size, stats_describe) while others are verb phrases (format_citation, list_products). The naming is clear but not perfectly uniform.

Tool Count5/5

With 8 tools, the server covers two functional domains (statistics and product browsing) without being bloated. Each tool serves a clear purpose, and the count feels well-scoped.

Completeness4/5

The product domain is covered thoroughly (list, free skill, paid skill, full product). The statistics domain is missing hypothesis tests and more advanced analyses, but the included tools cover basic descriptive, confidence intervals, and sample size planning, which is reasonable for a 'research desk' scope.

Resources

Need Help?