Skip to main content
Glama
Sign In

Clueso

by io.clueso
OverviewDiscussionsAdmin

Get design guide

get_design_guide
Read-only

Clueso's design guide, the HTML animation pages guide and the Director's skills. Ask for everything you need in ONE call. Each select entry is a section path or plain words; words search all three and return the best few, each labelled with the path that selects it exactly.

get_design_guide({select: ['gist', 'styles.kinetic-type', 'motion.*', 'stagger from the centre']})

Paths: 'gist' (the design gist and its contents; also what no arguments returns); design sections ('motion.camera', 'x.' with its children, '' for all); 'animation' (the pages guide's core), 'animation.gist', 'animation.' ('animation.craft.seams', 'animation.examples.hero'); 'skills', 'skills.'; the run_script stdlib: 'stdlib' (overview and modules), 'stdlib.anim', 'stdlib.native.tween', 'stdlib:'. One header per entry; anything past the size budget is listed by path for your next call. topic: 'pages' returns the whole guide for writing and editing HTML animation pages (read_animation / edit_animation); with select, only those sections. topic: 'skills' lists the Director's skills, the motion, design and animation craft notes on its computer; pass skill (and path) to read one.

Brand: pass project_id (or brand_kit_id) and the reply starts with a short 'brand' section: the brand kit's palette by role, each font role's exact font_setting, its logos (id, kind, for_background, aspect, url) and its guidelines. Follow it by default. 'brand.' returns one section in full as JSON with its edit link: overview, company (product knowledge), palette, logos, fonts, reference_images, guidelines, icons, captions, voices; 'brand.*' for all. Use an item by reference: a logo → add_elements element_type 'image' with src = that logo's url (match for_background to what is behind it; never recolor); a color role → its hex (palette.accent); a font role → its font_setting. List kits with find(type='brand_kits'); set a project's kit with update_project brand_kit_id. Building from a clueprint: pass its clueprint_id too, and the brand section says which of the two decides what (the kit: identity; the clueprint: format).

Input Schema

NameRequiredDescriptionDefault
pathNotopic 'skills' with skill: a file inside it, e.g. 'references/x.md'.
skillNotopic 'skills': a skill's name from the list; returns its SKILL.md and its files.
topicNo'design' (default): the house style, shaped by select. 'pages': authoring HTML animation pages. 'skills': the computer's skills, for inspiration.
selectNoEverything to return, in one list: section paths and plain words, mixed. 'brand' and 'brand.<section>' read the brand kit.
project_idNoThe project you are designing: adds its brand kit (the project's own, else the workspace default) as the 'brand' section.
brand_kit_idNoRead this brand kit (an id from find(type='brand_kits'), or 'default') instead of the project's: for a project on another kit, or a co-branded scene.
clueprint_idNoThe clueprint this project is built from: the brand section then says what it decides (format) and what the kit decides (identity), and whether it is brand_locked.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / path
      Added value: +{
+  "description": "topic 'skills' with skill: a file inside it, e.g. 'references/x.md'.",
+  "type": "string"
+}
    • removedInput schema / properties / query
      Removed value: -{
-  "description": "With topic 'stdlib': what to search for.",
-  "maxLength": 200,
-  "type": "string"
-}
    • addedInput schema / properties / skill
      Added value: +{
+  "description": "topic 'skills': a skill's name from the list; returns its SKILL.md and its files.",
+  "type": "string"
+}
    • changedInput schema / properties / topic / description
      Previous value: -"Older form; select covers it. 'animation': the animation guide's gist. 'stdlib': search with query."New value: +"'design' (default): the house style, shaped by select. 'pages': authoring HTML animation pages. 'skills': the computer's skills, for inspiration."
    • changedInput schema / properties / topic / enum
      Previous value: -[
-  "design",
-  "animation",
-  "stdlib"
-]New value: +[
+  "design",
+  "pages",
+  "skills"
+]
  2. Changed4 schema fields changed
    • addedInput schema / properties / brand_kit_id
      Added value: +{
+  "description": "Read this brand kit (an id from find(type='brand_kits'), or 'default') instead of the project's: for a project on another kit, or a co-branded scene.",
+  "type": "string"
+}
    • addedInput schema / properties / clueprint_id
      Added value: +{
+  "description": "The clueprint this project is built from: the brand section then says what it decides (format) and what the kit decides (identity), and whether it is brand_locked.",
+  "type": "string"
+}
    • addedInput schema / properties / project_id
      Added value: +{
+  "description": "The project you are designing: adds its brand kit (the project's own, else the workspace default) as the 'brand' section.",
+  "type": "string"
+}
    • changedInput schema / properties / select / description
      Previous value: -"Everything to return, in one list: section paths and plain words, mixed."New value: +"Everything to return, in one list: section paths and plain words, mixed. 'brand' and 'brand.<section>' read the brand kit."
  3. Changed3 schema fields changed
    • addedInput schema / properties / query
      Added value: +{
+  "description": "With topic 'stdlib': what to search for.",
+  "maxLength": 200,
+  "type": "string"
+}
    • addedInput schema / properties / select
      Added value: +{
+  "description": "Everything to return, in one list: section paths and plain words, mixed.",
+  "items": {
+    "maxLength": 120,
+    "minLength": 1,
+    "type": "string"
+  },
+  "maxItems": 40,
+  "minItems": 1,
+  "type": "array"
+}
    • addedInput schema / properties / topic
      Added value: +{
+  "description": "Older form; select covers it. 'animation': the animation guide's gist. 'stdlib': search with query.",
+  "enum": [
+    "design",
+    "animation",
+    "stdlib"
+  ],
+  "type": "string"
+}
  4. Changed4 schema fields changed
    • removedInput schema / properties / context
      Removed value: -{
-  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
-  "type": "string"
-}
    • removedInput schema / properties / conversation_id
      Removed value: -{
-  "description": "Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it.",
-  "type": "string"
-}
    • removedInput schema / properties / llm_model
      Removed value: -{
-  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
-  "type": "string"
-}
    • removedInput schema / required
      Removed value: -[
-  "context",
-  "llm_model"
-]
  5. Changed4 schema fields changed
    • addedInput schema / properties / context
      Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
    • addedInput schema / properties / conversation_id
      Added value: +{
+  "description": "Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it.",
+  "type": "string"
+}
    • addedInput schema / properties / llm_model
      Added value: +{
+  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
+  "type": "string"
+}
    • addedInput schema / required
      Added value: +[
+  "context",
+  "llm_model"
+]
  6. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  7. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, closed-world, non-destructive, so the safety profile is covered. The description adds genuine behavior beyond that: the size budget with overflow listed by path for a follow-up call, the reply leading with a short 'brand' section, and the instruction to follow the brand kit by default. Missing only return-shape detail, which is minor for a read tool with no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded and informationally dense—nearly every sentence carries a distinct rule—but it reads as an undifferentiated wall with nested quotes and colons, making the path grammar and the brand rules slow to extract. Sub-headers or bullets per topic would preserve the content at half the parse cost.

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?

All seven optional parameters are accounted for (path, skill, topic, select, project_id, brand_kit_id, clueprint_id), including the interaction between clueprint and brand kit (format vs identity, brand_locked). Default behavior with no arguments is stated, and the overflow behavior is disclosed, so an agent can call this correctly with no guesswork.

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 would be 3. The description earns more by defining the select path grammar that the schema only hints at ('motion.camera', 'x.*' with children, 'stdlib:<words>', plain words searching all three and returning the path that selects them exactly), and by enumerating brand.<section> values. It also states the constraint on logo reuse (match for_background, never recolor), which no schema field conveys.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence names the three resources it serves (the design guide, the HTML animation pages guide, and the Director's skills) and the 'topic'/'select' framing makes the retrieval model concrete. It is clear enough to distinguish from read_animation/edit_animation, which it explicitly pairs rather than replaces. The only weakness is that the title 'Get design guide' undersells the skills/pages/brand scope, so the agent must read past the name.

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 'Ask for everything you need in ONE call' plus worked example, plus per-topic routing ('pages' returns the whole guide for writing/editing; 'skills' lists then read one with skill+path). It also resolves the project_id vs brand_kit_id choice ('for a project on another kit, or a co-branded scene') and when to add clueprint_id. That is when-and-which guidance, not just what.

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

All Clueso toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources