Skip to main content
Glama

List sessions, sources, style presets and 3D/motion components

inspo_catalog

Browse past project sessions, scrape design sources, review style presets, and explore built-in 3D/WebGL, motion, text, cursor, and layout components from one catalog.

Instructions

Everything inspo can offer: past sessions in this project, scrape sources, style presets (with palettes/fonts), and the built-in live component library (3D/WebGL, motion, text, cursor, layout).

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": "inspo_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.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 alone. It usefully discloses the categories of content returned, which substitutes partly for the missing output schema, but says nothing about read-only/side-effect behavior, response size, or whether sessions are project-scoped versus global. For a zero-parameter listing tool the risk is low, so this is adequate rather than deficient.

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?

A single front-loaded sentence that packs the resource inventory into a scannable list with no filler. The parenthetical groupings (palettes/fonts, 3D/WebGL) add useful precision at low cost.

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 no-param, no-annotation, no-output-schema catalog tool, the description covers the essential unknown — what comes back — by naming the four content categories. Only a note establishing it as the discovery entry point for the sibling tools 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?

The tool takes no parameters, so the baseline is 4; there is no argument semantics for the description to explain. It correctly avoids inventing filter options that do not exist in the empty 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 description enumerates exactly what the tool surfaces: past sessions, scrape sources, style presets with palettes/fonts, and the built-in component library (3D/WebGL, motion, text, cursor, layout). That is specific enough to distinguish it from the add_*/harvest/search siblings, which operate on single resource types. The verb is implicit ('Everything inspo can offer') rather than stated, so it falls just short of a 5.

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

Usage Guidelines2/5

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

There is no when-to-use statement, no mention that it should be called first as a discovery step before inspo_add_component or inspo_add_styles, and no exclusions or alternatives named. The catalog/discovery intent is only inferable from the enumeration itself.

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