Skip to main content
Glama

list_starters

Read-only

Read-only. Siteon's starter sites (key scope sites:read): 9 industries × 1-3 moods, each in two layouts (single: one page with sections; multi: a top page and sub pages). For each: id, industry, mood, tags (words to match the person's words), palette, fonts, hero and nav style, the forms / CMS collections it uses, its pages. How big a starter is shows in layouts..pages (the page count of that layout) and collections (the CMS collections it needs), so you can match it to the site's plan: a site on Mini (3 pages, no CMS) needs one of the small starters (shop-, solo-, event-*), which carry no CMS collection at all; the others want Standard or above. Pick one from the person's industry and the mood words they used (or two to let them choose); do not show this list raw. Then get_starter (to read) or start_from_starter (to build).

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

Input Schema

NameRequiredDescriptionDefault
moodNoOnly this mood (e.g. warm, modern)
industryNoOnly this industry (restaurant, salon, gym, clinic, office, corporate, shop, solo, event)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / industry / description
      Previous value: -"Only this industry (restaurant, salon, gym, clinic, office, corporate)"New value: +"Only this industry (restaurant, salon, gym, clinic, office, corporate, shop, solo, event)"
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered; the description adds the required key scope (sites:read), the plan-tier constraint on results, and the catalogue's shape. It stops short of pagination/limit behavior, though the fixed 9-industry catalog makes that largely moot.

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 'Read-only' and scope, then the data shape, then the selection/next-step guidance. It is dense and long for a single paragraph, but nearly every clause carries actionable information; splitting the plan-tier rule into its own sentence would help.

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

Completeness5/5

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

No output schema exists, and the description compensates by enumerating the returned fields (id, industry, mood, tags, palette, fonts, hero/nav style, forms/collections, pages) and explaining where page-count and CMS data live. Combined with the plan-matching rule, an agent has everything needed to call and use the result.

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 100% with both filters documented, so the baseline is 3; the description adds real semantic value by explaining that tags are 'words to match the person's words' and that mood/industry should be derived from the user's language, which is 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?

States a concrete verb and resource ('Siteon's starter sites') and immediately explains the catalog's dimensions (industries × moods × two layouts) with what each entry contains. It also explicitly routes to the differentiation siblings: 'Then get_starter (to read) or start_from_starter (to build).'

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

Usage Guidelines5/5

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

Gives explicit selection logic ('Pick one from the person's industry and the mood words they used (or two to let them choose)'), an exclusion ('do not show this list raw'), and plan-based filtering rules (Mini needs shop-*, solo-*, event-*). It also names the follow-up tools and what each is for.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources