Moltline Educator Toolkit

Get Free Skill

get_free_skill

Read-onlyIdempotent

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

Typical input {"slug": "curriculum-architect-hs"} 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. "curriculum-architect-hs"; 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?

Beyond the annotations (readOnlyHint, idempotentHint, destructiveHint), the description adds that the tool never raises a protocol error, returns a structured error object with troubleshooting advice, and confirms that every call is read-only and idempotent, making retries safe. This is significant behavioral transparency.

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 concise (5 sentences) and well-structured: purpose first, then example, usage scope, error behavior, and idempotency. Every sentence adds value and there is 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 tool's simplicity (single parameter, output schema present), the description covers all necessary aspects: purpose, input, output example, error handling, usage context, and idempotency. It is fully self-contained and requires no further clarification.

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?

The input schema already has 100% description coverage for the 'slug' parameter, including the example and source. The description repeats this information (e.g., 'Product slug exactly as returned by list_products') and adds a sample output, but does not introduce new semantic meaning beyond what the schema provides. Baseline is 3.

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 'product's free gateway skill with its complete instructions'. It provides a typical input/output example and explicitly distinguishes this tool from the sibling 'get_full_skill', which is for other skills and requires 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?

The description says 'Use when the caller wants usable instructions immediately' and explicitly states what it is not for: 'Not for the product's other skills: those are named and need get_full_skill with a skill_name, which requires a paid plan.' This provides 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 Educator Toolkit 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.6/5.0

Disambiguation5/5

All seven tools have clearly distinct purposes. The three product/skill retrieval tools (get_free_skill, get_full_skill, get_full_product) are precisely differentiated by what they return. The remaining four tools (list_products, grade_curve, lesson_timer, readability_report) each target a unique function with no overlap.

Naming Consistency3/5

Tool names use a mix of verb_noun (get_free_skill, get_full_skill, list_products) and noun_noun (grade_curve, lesson_timer, readability_report) patterns. While each name is readable and the convention is not chaotic, the lack of a uniform pattern reduces consistency.

Tool Count5/5

Seven tools is a well-scoped count for an educator toolkit. Each tool addresses a distinct need: product discovery, skill retrieval, assessment analysis, lesson planning, and readability checking. No tool is superfluous, and the number feels complete without being overwhelming.

Completeness4/5

The tool surface covers the core domain: product listing, skill retrieval (free and paid), assessment statistics, lesson timing, and readability analysis. Minor gaps exist, such as the absence of a search or comparison feature across products, but the essential workflows are supported without dead ends.

Resources

Need Help?