Skip to main content
Glama
Sign In

Moltline Studio

by com.moltlinestudio
OverviewDiscussionsAdmin

Get Full Product

get_full_product
Read-onlyIdempotent

Load one product in full: persona plus every skill's instructions. PREMIUM (license).

Typical input {"slug": "inbox-commander"} 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 bundle of products (get_full_kit). 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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "get_full_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesProduct slug exactly as returned by search_catalog.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/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, and the description adds materially beyond them: a PREMIUM/license precondition, the non-throwing error contract (returns {"error": ...} rather than a protocol error), and the resulting safe-retry guarantee after correcting input. That is exactly the kind of operational context annotations cannot carry.

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?

Front-loaded with purpose, then a return-shape example, then routing exclusions, then error semantics — a sensible order with no filler. Minor deduction because 'Returns persona plus every skill for one product' restates the opening sentence almost verbatim, and the return-shape illustration is partly redundant with the existing output schema.

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?

For a one-param read tool with a full output schema and strong annotations, everything an agent needs is present: selection criteria, alternatives, a license caveat, and a non-standard error contract that would otherwise be a trap. Nothing material is missing.

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% and the single param already says 'exactly as returned by search_catalog', so the schema does the heavy lifting. The description adds a concrete example invocation ({"slug": "inbox-commander"}) and an error example ("unknown slug '<value>'") that clarifies the slug's expected shape and how failures surface, which is modest but real value beyond the 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?

States a specific verb and resource — 'Load one product in full: persona plus every skill's instructions' — and makes the scope distinction explicit against siblings get_full_skill (one skill) and get_full_kit (a bundle of products). An agent can route correctly without opening any schema.

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?

Gives a positive selection rule ('Use when the caller wants the whole product') and two named exclusions with the alternative that fits each case ('Not for a single skill (get_full_skill)... not for a bundle of products (get_full_kit)'). This is explicit when/when-not/alternative guidance.

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

All Moltline Studio toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources