Skip to main content
Glama

Moltline Educator Toolkit

by com.moltlinestudio

Get Full Product

get_full_product
Read-onlyIdempotent

Load one product in full: its persona plus every paid skill. PREMIUM (license).

Typical input {"slug": "curriculum-architect-hs"} returns {"slug": ..., "name": ..., "persona": "", "skills": [{"name": ..., "instructions": ...}, ...], "free_skill": {...}}.

Returns persona plus every skill for one product. Use when the caller wants the whole product. Not for a single skill (get_full_skill) and not for a free look, which list_products and get_free_skill provide with no plan. 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. "curriculum-architect-hs"; must be non-empty.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.9/5.0
Behavior5/5

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

Description adds significant behavioral details beyond annotations: error handling (never raises protocol error, returns error object), idempotency and retry safety, premium license, and exact return structure. Annotations already provide readOnlyHint and idempotentHint, but description enriches with practical usage behavior.

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?

Description is front-loaded with purpose, includes a clear example, usage guidelines, and error handling. Every sentence is informative and earns its place. No filler or redundancy. Highly efficient.

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 (one parameter, simple input, output schema exists), the description covers all essential aspects: purpose, usage, error behavior, idempotency, and license. The presence of output schema means return values are already documented. Complete for an AI agent to use correctly.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. Description adds meaning by giving an example slug value ('curriculum-architect-hs'), specifying format (exactly as returned by list_products), and clarifying that slug must be non-empty. Also explains error handling for invalid slugs. Adds value beyond schema.

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 full product with persona and paid skills, using a specific verb ('Load') and resource. It distinguishes from siblings by mentioning 'get_full_skill' and 'list_products' for different use cases.

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?

Explicitly states when to use ('caller wants the whole product') and when not to use (single skill -> get_full_skill, free look -> list_products/get_free_skill). Also mentions premium license requirement, guiding the agent on context.

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 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.7/5.0
Disambiguation5/5

All seven tools target distinct actions: product discovery (list_products), free skill retrieval (get_free_skill), paid skill retrieval (get_full_skill), full product details (get_full_product), assessment analysis (grade_curve), lesson timing (lesson_timer), and text readability (readability_report). No overlap or ambiguity.

Naming Consistency5/5

All tools use a consistent verb_noun pattern in snake_case: get_free_skill, get_full_product, get_full_skill, list_products, grade_curve, lesson_timer, readability_report. The naming is predictable and intuitive.

Tool Count5/5

With 7 tools, the server is well-scoped for an educator resource provider. It covers product access (4 tools) and three distinct pedagogical utilities, without unnecessary bloat or deficiency.

Completeness5/5

The tool surface covers the full lifecycle for its domain: product discovery, free and paid skill access, full product retrieval, plus three distinct teaching utilities (assessment summary, lesson timing, readability). No obvious gaps for a read-only resource server.

Resources