Skip to main content
Glama

Resource catalog

list_resources
Read-only

Lists cataloged design resources and shows whether each is covered by an MCP tool, has an official MCP, or is just a link, so you can find inspiration or choose the right tool.

Instructions

Lists the design resources in the catalog (references, images, components, icons, fonts, motion, 3D, audio...). The access field says whether a tool in this MCP covers it (tool:...), whether it has an official MCP (mcp), or whether it is just a link. Use it to suggest where to find inspiration or which tool to use.

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_resources"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoSearch by name
pricingNo
categoryNoFilter by category, e.g. Icons, Fonts, Motion

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description goes further by documenting the semantics of the returned `access` field (tool:…, mcp, or just a link), which is genuinely useful output-shape context given there is no output schema. It omits result volume/pagination and whether listing is exhaustive, which keeps it from a 5.

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?

Three sentences, front-loaded with what is listed, then the key output field, then the usage cue — no filler. Slightly list-heavy but the parenthetical category enumeration earns its space by conveying catalog scope.

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?

For a read-only catalog lister whose safety profile is covered by annotations, the description supplies the missing pieces: catalog breadth and the meaning of the `access` values. With no output schema, more detail on return shape (grouping, count) would help, but nothing essential to correct invocation is absent.

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 67% and the description supplements it by listing the category vocabulary (icons, fonts, motion, 3D, audio), which helps the caller infer valid `category` values that the schema only illustrates with three examples. It says nothing about `query` matching rules or how `pricing` interacts with results, so the gain is modest.

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 ('Lists the design resources in the catalog') and enumerates the categories covered (references, images, components, icons, fonts, motion, 3D, audio). It also hints at its routing role ('which tool to use'), though it never names the search_* siblings it overlaps with, so differentiation is implied rather than explicit.

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?

Offers a use case — 'suggest where to find inspiration or which tool to use' — which implies this is a discovery/browsing entry point rather than a targeted lookup. However, it gives no when-not guidance and does not contrast with the more specific search_icons/search_fonts/search_images tools, leaving the agent to infer that a targeted query should go elsewhere.

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