Skip to main content
Glama

Clueso

by io.clueso
OverviewDiscussionsAdmin

Get design guide

get_design_guide
Read-only

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

get_design_guide({select: ['gist', 'styles.kinetic-type', 'motion.*', 'animation.contract', '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.gist' (the animation guide's gist and contents), 'animation' (its core) or 'animation.'; 'stdlib' (its modules), 'stdlib.' or 'stdlib.' ('stdlib.native.tween'). Start with select ['gist', 'animation.gist', ...] for both gists. One header per entry; anything past the size budget is listed by path for your next call. (topic/query still work.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoWith topic 'stdlib': what to search for.
topicNoOlder form; select covers it. 'animation': the animation guide's gist. 'stdlib': search with query.
selectNoEverything to return, in one list: section paths and plain words, mixed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+}
  2. 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"
-]
  3. 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"
+]
  4. 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"
  5. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed world), so the description's added value is the truncation/budget behavior ('anything past the size budget is listed by path for your next call') and how entries are labelled. It does not describe auth or rate limits, but that is minor for a read-only doc fetch.

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 and an example, then path grammar. Most sentences carry necessary information, but the layout is jumbled — inline code, a trailing terse '(topic/query still work.)', and legacy notes interrupt the flow rather than sitting in a clean order.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the return-value burden and largely meets it: one header per entry, labelled by the path that selects it, with overflow listed by path. Combined with the path grammar, an agent has enough to call it correctly on the first try.

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 already 100%, yet the description meaningfully enriches the select grammar: wildcards ('motion.*'), exact paths, the 'gist'/'animation.gist'/'stdlib.<member>' forms, and free-word search that resolves to labelled paths. It also clarifies that topic/query are legacy forms superseded by select — real semantic value beyond the schema.

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 states the resource precisely — it retrieves Clueso's design guide, animation guide, and animation stdlib — and the example shows the exact call shape. It is clear what the tool returns, though it never explicitly contrasts itself with plausible siblings like read_animation or get_element_schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives concrete usage direction: 'Ask for everything you need in ONE call' and 'Start with select [gist, animation.gist, ...] for both gists.' This tells the agent how to drive the tool efficiently, but there are no explicit when-not-to-use conditions or named alternatives.

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