Skip to main content
Glama
Sign In

SHIP

by ai.letsship
OverviewDiscussionsAdmin

List brand presets

list_brand_presets
Read-onlyIdempotent

List the six preset looks of a site: the colors, the fonts and the shape of the mark of each one. Pass an id as site.brand.presetId with the brand source preset. With set kits, list only the three brand kits that the site form offers a founder.

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

Input Schema

NameRequiredDescriptionDefault
setNoall (the default): the six looks. kits: the three brand kits

Output Schema

NameRequiredDescriptionDefault
dataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already establish the safe read-only, idempotent, non-destructive profile, so the description mainly needs to add scope. It contributes exact cardinality (six vs three presets) and the downstream purpose of the returned id (consumed as site.brand.presetId), which is real added context, but nothing about ordering, stability, or whether presets are tenant-customizable.

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

Conciseness3/5

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

Three sentences, front-loaded with the core action, and no filler. However, the middle sentence ('Pass an id as site.brand.presetId with the brand source preset') is syntactically ambiguous — it reads like an invocation instruction for a tool that takes no such parameter — which costs clarity.

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?

With an output schema present, the description need not document return shape, and it correctly stops at describing what the presets are and how the id is reused. For a zero-required-parameter read tool this is essentially complete, missing only guidance on ordering or stability of the returned ids.

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% and the single enum parameter is already fully documented with both values and the default. The description restates the same all/kits split and adds only the gloss that the kits are the ones the site form offers a founder, so it adds marginal meaning over the 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 gives a specific verb and resource ('List the six preset looks of a site') and immediately enumerates what each look contains (colors, fonts, shape of the mark). It also distinguishes the two modes (six looks vs three brand kits). It falls short of 5 only because the 'site.brand.presetId' sentence muddles the statement of what the tool itself does.

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?

It clarifies the set=kits mode ('list only the three brand kits that the site form offers a founder'), which implies when that variant applies. It does not state when to prefer this over an alternative, nor the practical consequence of leaving the parameter at its default beyond restating the schema default. Usage is implied rather than guided.

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

All SHIP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources