Skip to main content
Glama
Sign In
coss-ui-mcp

coss-ui-mcp

by Zoot01
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

coss_list_components

Fetch a concise list of design system components, hooks, and overview sections to quickly identify which to explore in detail.

Instructions

List the coss ui catalog (components, hooks, or overview docs) with one-line descriptions. Cheap overview — call before fetching full docs.

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

Input Schema

NameRequiredDescriptionDefault
sectionNoWhich catalog section to list. Default: components.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description must cover behavioral traits. It mentions 'cheap overview' indicating low cost, but does not disclose potential outcomes, pagination, or permissions. Adequate but not comprehensive.

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

Conciseness5/5

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

Two concise sentences. The first states purpose, the second provides usage guidance. No unnecessary words, front-loaded with key information.

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 simple list tool with one parameter and no output schema, the description is fairly complete. It covers purpose, parameter, and usage hint. It could mention return format explicitly, but 'one-line descriptions' implies it.

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 coverage is 100% (parameter has enum and default described). The description adds context about listing sections (components, hooks, overview) and one-line descriptions, but does not significantly extend beyond the schema.

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

Purpose5/5

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

The description clearly states the tool lists the coss UI catalog (components, hooks, or overview docs) with one-line descriptions. It distinguishes from sibling tools like coss_get_component (detailed fetch) by noting it's a cheap overview.

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?

The description advises 'call before fetching full docs,' providing clear usage context. It implies when to use but does not explicitly mention when not to use or alternatives.

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

Deploy Server

Other Tools