Skip to main content
Glama

list_asset_sets

Lists available Wonderdraft symbol sets with keys, names, categories, pack and variant counts. Query by key or name or filter by category to find the set to use before adding symbols.

Instructions

List symbol sets: key (pass to add_symbol etc.), name, category (symbols|mountains|trees), pack and variant count. query matches key or name.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_asset_sets"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden, and it does disclose the response shape (key, name, category, pack, variant count) and that query matches key or name. It omits matching semantics (exact versus substring, case sensitivity), the default limit of 50, and whether results are truncated, which matter for a list tool.

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?

Two short sentences with the resource and returned fields front-loaded, and no filler. The telegraphic style is slightly dense but every clause carries information.

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

Completeness3/5

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

With no output schema, no annotations, and 0% schema description coverage across three parameters, the description does useful work by naming the return fields and the category vocabulary. It is still incomplete on result-set limits and matching behavior, which an agent would need to call it predictably.

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?

Schema description coverage is 0%, so the description must compensate. It explains two of the three parameters — query ('matches key or name') and category (enumerating symbols|mountains|trees) — meaningfully beyond the bare schema, but says nothing about limit or its default of 50.

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?

States a specific verb and resource ('List symbol sets') and immediately enumerates the fields returned (key, name, category, pack, variant count), which lets an agent distinguish it from sibling viewers such as list_objects and list_themes. It stops short of explicitly naming those siblings, so it is clear but not fully differentiated.

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

Usage Guidelines3/5

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

Usage is only implied: the parenthetical 'key (pass to add_symbol etc.)' hints at the intended workflow of resolving a key before calling a mutation tool. There is no explicit statement of when to use this versus list_themes or list_objects, and no exclusions or prerequisite conditions.

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